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

The description adds substantial behavioral context beyond the annotations: it mentions that the operation is asynchronous ('status: 'completed' | 'in_progress''), explains the polling mechanism via get_site_status, and mandates serial execution. This goes far beyond the simple readOnlyHint/destructiveHint annotations.

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 concise, well-structured, and front-loaded. Every sentence earns its place: it states the purpose, usage trigger, required params, return value, polling instructions, and concurrency warning without unnecessary filler.

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?

Given the tool's complexity (async operation, reassembly of pages, concurrency constraints) and the absence of an output schema, the description fully covers return values, polling pattern, and operational constraints. It is complete enough for an agent to invoke and monitor the tool correctly without further clarification.

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?

The input schema already provides 100% coverage with descriptions for all three parameters (businessId, versionId, pageId). The description repeats which are required but adds no additional semantic meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 footer of a WebZum site' with specific actions ('Creates a new version with a fresh AI-generated footer and reassembles every page'). It distinguishes from sibling tools like regenerate_header and regenerate_logo by focusing on footer-specific behavior.

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 when-to-use guidance ('Use when the user wants different footer content, layout, or copy') and includes a clear concurrency constraint ('Never fire parallel edit calls on the same site'). While it doesn't explicitly name alternatives, the tool's scope is well-defined and does not overlap confusingly with siblings.

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