updateTemplatePage

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

Description adds context beyond annotations: automatic history recording and parent template date update. Annotations already indicate destructive (true), idempotent (true), and open world (true), with no contradictions.

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?

Three sentences, front-loaded with purpose, then parameters and behavioral notes. No waste, but could be slightly more 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?

Covers purpose, parameters, side effects, and related tools. Missing error handling or permission prerequisites, but overall sufficient for a mutation tool with annotations.

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 covers 67% top-level descriptions; description adds that page_type enums match getTemplatePage and mentions character limits, but mostly restates schema details. Adds marginal value.

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?

Description clearly states it updates HTML/CSS source for a template page, specifying verb and resource. It distinguishes from siblings like getTemplatePage (retrieve) and getTemplatePreview (preview).

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?

Description provides explicit guidance on when to use and alternatives: references getTemplatePage for current values, getTemplatePreview for browser display, and getTemplates for template list.

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