Save a test page

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

The description adds 'overwrite' behavior beyond annotations (idempotentHint=true, destructiveHint=false), but this actually contradicts destructiveHint=false because overwriting is destructive to the existing file. No other behavioral details (auth, output, side effects) are provided, leaving ambiguity.

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?

Single sentence that directly states the purpose without fluff. Information is front-loaded and each word adds value. Perfectly concise for a tool with three parameters.

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?

Despite low complexity (3 required params, no output schema), the description omits critical details: parameter expectations, error conditions, return value, and relationship to sibling tools like 'add_page'. Agents lack sufficient information to use it correctly without guessing.

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 only 33% (only 'name' has a description). The description does not explain the 'html' or 'project' parameters, nor provide format or constraints. It minimally implies 'html' is the content, but fails to compensate for the low schema coverage.

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 specifies a clear verb ('Create/overwrite') and resource ('standalone HTML test/QA page') under a specific folder ('project's test-pages/'). This distinguishes it from sibling tools like 'add_page' (general page) and 'get_test_page' (read).

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?

No guidance on when to use this tool versus alternatives. It does not mention exclusivity to test pages, conditions for overwriting, or distinguish from 'add_page' or 'save_media'. The annotation 'idempotentHint=true' is already structured, but the description fails to add usage context.

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