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

The 'Read' verb aligns with the readOnlyHint=true, idempotentHint=true, and destructiveHint=false annotations, with no contradiction. It adds only the workspace scope and reuse intent, not deeper behavioral details such as matching semantics, ordering, or rate limits; the annotations already carry the safety profile.

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 entire description is a single front-loaded sentence that starts with the operation ('Read') and resource before stating the purpose. Every clause earns its place, with no filler or repetition of the title or schema.

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?

This is a simple, optional-parameter read operation with strong annotations covering safety and idempotency, plus a complete schema. No output schema is present, and for a list/detail template tool no return-format details are necessary for correct invocation, so the description is complete.

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?

Both parameters are fully described in the schema ('Match on template name' and 'Return one template in full'), giving 100% schema description coverage. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 an explicit verb ('Read') and resource ('the workspace's saved email templates'), and explains the intended outcome ('so a campaign can reuse proven copy'). This clearly distinguishes it from sibling tools like list_campaigns or get_inbox by naming the specific object type.

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 phrase 'so a campaign can reuse proven copy' communicates the main use case for retrieving templates when preparing a campaign. It does not explicitly name alternative tools or state exclusions, but no sibling tool targets template retrieval, so the implied context is sufficient.

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