Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only state readOnlyHint=false and destructiveHint=false. The description adds real behavioral context beyond them: 'change' rewrites pages and puts them live, and requires a preview-then-confirm step. That the live-publish consequence is disclosed is valuable for a mutation action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the resource definition and then walks the action modes in order, with the confirmation caveat attached to 'change'. It is information-rich with little waste, though slightly packed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 4 params, the description covers the mutation flow and confirmation requirement adequately. It is a bit thin on what 'enquiries' returns and on org-scoping behavior, but nothing essential to invoking it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: 'org' and 'confirm' are documented in-schema while 'action' and 'instruction' are not. The description compensates by explaining the enum values in detail and the meaning of 'instruction' for the change action, adding meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (the site Seovyn hosts for a business without its own website) and enumerates the three action modes with concrete outcomes. An agent can tell it manages a hosted site, but it never names or contrasts any sibling tool to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It maps each action to its use case ('get' default, 'change' for rewrites, 'enquiries' for contact-form messages) and flags that 'change' needs confirmation. It gives clear operational context but offers no exclusions or named alternatives among the many siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.