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

The description discloses important behaviors beyond annotations: it creates a new version, reassembles every page, returns a status with polling instructions, and mandates serial concurrency for the same businessId. This adds significant context that annotations (readOnlyHint=false, destructiveHint=false) do not cover.

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?

The description is well-structured and front-loaded with purpose, followed by usage, return behavior, and concurrency. Every sentence provides necessary information with no redundancy, making it appropriately concise.

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, the description explains the return value and polling behavior. It also covers concurrency requirements and the overall effect on the site. Given the tool's complexity and the presence of three well-documented parameters, the description is fully complete for an agent to use correctly.

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 description coverage is 100%, so the baseline is 3. The description does not add extra meaning beyond what the schema already provides, merely repeating the required parameters. The schema descriptions themselves are adequate, so no deduction is warranted.

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 clearly states the tool's function: "Regenerate the header (nav bar, logo placement, top-of-page) of a WebZum site." It uses a specific verb ('regenerate') and resource ('header') and explicitly distinguishes from siblings like regenerate_footer and regenerate_logo by specifying the header scope.

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?

The description provides explicit usage context: "Use when the user wants the nav restyled, links reordered, or the header redesigned." This gives clear guidance on when to use the tool, though it does not explicitly mention alternatives or exclusions, so it falls short of a perfect 5.

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