Export from Template

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is well-covered. The description adds no additional behavioral context beyond stating it generates an export, which is consistent with the annotations. 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?

The description is a single sentence that front-loads the usage context ('Use this when') and conveys the core function with no wasted words. It is appropriately short and efficient.

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?

Given that annotations provide safety information, the input schema fully documents parameters, and an output schema exists (implied by context signals), the description is complete enough. It tells the agent when and how to use the tool, and the remaining details are covered by structured fields.

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 100%, meaning the input schema already describes all three parameters fully. The tool description adds no extra parameter information beyond what is in the schema. Based on the rubric, a baseline score of 3 applies when schema coverage is high and description does not enhance understanding.

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 verb 'generate' and the resource 'previously saved template' with a specific date range. This naturally distinguishes it from sibling tools like 'export_generate' (which likely exports without a template) and 'export_template_list' (which lists templates). The purpose is unambiguous.

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?

The description explicitly says 'Use this when the user wants to generate an export using a previously saved template', providing a clear when-to-use. However, it does not explicitly mention when not to use or name alternatives, though the context of sibling tools makes the distinction clear.

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