get_template_default_content

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

Even without annotations, the description fully discloses behavior: read-only, safe to retry, max 10 concurrent requests, authentication required, and returns 404 for invalid template_id. This compensates for the lack of 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?

Well-structured with front-loaded purpose, followed by usage, behavioral notes, parameter description, and return description. Every sentence adds value, though slightly verbose in places.

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 all essential aspects: purpose, usage, constraints, parameter, and output format. Includes error case. For a simple retrieval tool with no output schema, it provides sufficient information for an agent.

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 template_id is explained with format and source ('numeric string, e.g. '12345'. Obtain from list_templates'), adding essential meaning beyond the schema which only specifies type string. 0% schema coverage is fully compensated.

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 explicitly states 'Retrieve the default HTML content of a template for use in campaign content', clearly indicating the action (retrieve) and resource (template). It differentiates from siblings by referencing list_templates and set_campaign_content.

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?

Provides clear when-to-use guidance: 'Use to extract a template's HTML before customizing it with set_campaign_content'. Also notes limitations for gallery templates and mentions using list_templates to find IDs. Does not explicitly state when not to use, but the context is clear.

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