Export Website

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that the build is local-only and includes every tree, but says nothing about where output lands, whether it overwrites a prior build, or how long it takes.

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?

One efficient sentence with the core action front-loaded and no filler. 'Chooser' is unexplained jargon, but the sentence does not waste words.

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?

An output schema exists, so return values need not be described, and the local-build/no-deploy behavior is clear. The remaining gap is the undocumented hide_living flag, which materially changes what gets exported.

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 single parameter hide_living (boolean, default true) has 0% schema description coverage and is not mentioned in the description. With no documentation anywhere, an agent cannot tell that this controls whether living people are excluded from the export.

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?

States a specific action (build the complete site locally) and scopes it ('including chooser and every tree'). The phrase 'without deploying' implicitly separates it from publish_site, though no sibling is named.

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?

'Without deploying' hints at when to prefer this over publish_site, but the guidance is indirect. There is no explicit statement of when to use this versus publish_site or configure_website, and no prerequisites mentioned.

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