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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context about what the payload contains beyond a bare record (per-network overrides and network options), but says nothing about authorization requirements or behavior when the ID is unknown or out of scope for the organization.

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?

A single sentence with zero filler. The identifying action ('Fetch a single template by ID') is front-loaded and the return-content clause follows, so the agent reads the essential fact first.

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 two-parameter read tool with full schema coverage, annotations covering safety, and an output schema that documents return shape, so the description needn't explain return values. It is nearly complete; the only missing piece is routing guidance toward list_templates when the ID is unknown.

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%, so both templateId and organizationId are already documented, including the multi-org conditional rule. The description only reinforces that lookup is by ID and adds no syntax, format, or scoping detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 and resource: 'Fetch a single template by ID', and it enumerates what the return includes (per-network text/media overrides and network options). It is clearly distinguishable from create_template/update_template/delete_template by the read verb, but it never names list_templates as the sibling that enumerates templates, so the differentiation is only implicit.

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?

Usage is implied by 'by ID' — the agent can infer this is for retrieving one known template rather than browsing — and the schema note '(from list_templates)' points at the prerequisite. However, the description itself states no when-to-use, no when-not-to-use, and no explicit alternative for discovery.

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