Update Export Template

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description confirms it is a modification operation but adds no further behavioral details (e.g., partial update behavior, permissions, side effects). With annotations present, the description provides minimal added value, but it does not contradict them.

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, front-loaded sentence that clearly states the tool's purpose. It is concise and efficient, though it could benefit from slightly more context without becoming verbose.

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 output schema exists and input schema is fully described, the description is adequate but minimal. It does not mention that only provided fields are updated (implied by the schema), nor does it address the openWorldHint annotation. For a 6-parameter tool, additional context about partial updates would improve completeness.

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?

Input schema has 100% coverage, with each parameter described. The description adds no additional meaning beyond what the schema provides. Baseline 3 is appropriate; the description does not compensate for any schema gaps as there are none.

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 'modify an existing export template' with a specific verb ('modify') and resource ('export template'). This distinguishes it from sibling tools like export_template_create, export_template_delete, and export_template_get, allowing an agent to correctly select it for update actions.

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 specifies when to use the tool ('when the user wants to modify an existing export template') but provides no guidance on when not to use it or alternatives. Sibling tools for creating, deleting, or listing templates exist but are not mentioned, limiting the agent's ability to differentiate use cases.

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