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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds only the backup/migration intent and a caution about not hand-building the template; it says nothing about the export payload format or size, so it adds modest value beyond the 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?

Two sentences, front-loaded with the core purpose followed by the workflow caveat. There is no filler, though the second sentence is slightly indirect in tying back to this specific tool.

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?

For a simple one-parameter read tool with rich annotations, the definition is close to sufficient. But with no output schema, the description never indicates that the result is a reusable template payload, which is the one piece of context an agent would want before invoking it.

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?

There is a single parameter (agentId) with 100% schema description coverage, so the schema already carries the semantics. The description adds no additional detail about agentId, which is the expected baseline when the schema does the work.

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 gives a specific verb and resource ('Export an agent template') plus a reason (backup or migration), so an agent can tell it apart from mutation siblings like update_agent or clone_agent. It does not, however, explicitly contrast with the closest sibling import_agent.

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?

It states when to use the tool ('for backup or migration') and adds a concrete directive to use the dedicated OpenAPI routes rather than manually reconstructing the template shape. It stops short of naming specific alternatives such as import_agent or clone_agent.

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