Export all ZeptoMail templates from one Agent

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description reinforces these by saying 'Read-only' and adding valuable clarification that the tool does not write to disk—the caller handles file writing. This goes beyond the annotations by explicitly addressing side-effect expectations.

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 deliver both the functional scope and the usage context with no wasted words. The key behavior is front-loaded, and the clarifying 'does not write to disk' earns its place in the same sentence.

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-only export tool, the description covers what is returned, the scope, the caller's responsibility, and the primary use case. It does not describe output size or pagination, but the absence of an output schema and the straightforward nature of the operation make this adequate.

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 description coverage is 100% and the sole parameter agentKey is already well documented as an exact mailagent_key/alias returned by zeptomail_list_agents. The description mentions 'one explicit Agent' but adds no new parameter-level meaning beyond the schema.

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 uses a specific verb 'Fetch' with a precise resource: every full template from one explicit Agent, returned as a single JSON dump. It lists the exact fields included, which clearly distinguishes it from sibling list/find/get tools even without naming them.

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 states the intended use case: backing up an Agent's templates to local files, and clarifies that the caller writes files while this tool only returns data. It does not explicitly name alternatives or say when not to use it, but the use-case framing provides clear directional guidance.

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