get_template_default_content

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

Discloses authentication via API key, max 10 concurrent requests, read-only safe to retry, and 404 error for invalid template_id. No annotations exist, so description carries full burden and meets it comprehensively.

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?

Concise with 4 sentences plus structured Args/Returns. Every sentence adds value; no redundancy.

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, usage, parameters, behavioral constraints, and return format (html string and sections object). Output schema exists but description supplements it. Complete for a simple read tool.

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?

Adds meaning beyond the schema: provides format (numeric string), example ('12345'), and source (list_templates). Schema coverage is 0%, so description fully compensates.

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 retrieves the default HTML content of a template, with specific verb and resource. It distinguishes from siblings like get_template (metadata) and set_campaign_content (customization).

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?

Explicitly states when to use (before customizing with set_campaign_content), limitations (gallery templates may have limited content), and alternative tool (list_templates to find IDs).

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