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

With no annotations, the description carries the full burden for behavioral disclosure. 'Get' clearly implies a read-only, idempotent operation, and specifying that it returns content and field definitions adds some transparency. However, it does not disclose error behavior, permissions required, or whether the template includes additional metadata beyond content and fields.

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, tight sentence with no filler. The verb and resource are front-loaded, and the inclusion of 'content and field definitions' provides value without adding length.

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 single-ID getter with one parameter, the description is minimally adequate: it states what the tool does and what the response covers. Yet without annotations or an output schema, it omits key context such as the ID format restrictions, not-found behavior, and relationship to sibling template tools, making it less complete than it could be.

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 0%, so the description must compensate for the lone 'id' parameter. Saying 'by ID' merely restates the parameter name and does not explain the required pattern (^[cC][^\s-]{8,}$) or provide guidance on how to obtain or format the ID. This leaves a meaningful gap for an agent trying to invoke the tool correctly.

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 a specific action ('Get') on a specific resource ('a specific template by ID') and even describes what is included in the result ('content and field definitions'). It distinguishes from listing or mutating templates, though it does not explicitly name sibling alternatives.

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 implies when to use this tool: when you need a single template by ID and want its content or field definitions. However, it provides no explicit guidance on when not to use it or how it differs from template_list, template_create, or template_update, leaving the routing decision mostly to inference.

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