get-exercise-template

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

Annotations already provide readOnlyHint=true, indicating a safe read operation. The description adds that it returns 'complete details' and lists fields, but does not disclose additional behavioral traits such as error handling, authentication needs, or rate limits. With annotations already covering safety, the description adds moderate value.

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 sentence of 18 words, front-loaded with the action and resource, and lists the fields concisely. Every word contributes value; no waste.

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 get-by-ID tool with one parameter, the description covers the purpose and return fields. It does not mention error cases or what happens if the ID is invalid, but given no output schema, it provides sufficient context for a straightforward read operation.

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. However, it only mentions 'by its ID' without explaining the format, source, or constraints of 'exerciseTemplateId'. The schema says minLength 1, but the description adds minimal meaning, leaving the parameter underspecified.

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 the tool retrieves complete details of a specific exercise template by ID, listing the fields included (name, category, equipment, muscle groups, notes). It distinguishes from siblings like 'get-exercise-templates' (plural) and 'search-exercise-templates' by focusing on a single template retrieval.

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 use when needing details of one template, but does not explicitly state when to use this tool versus siblings like 'get-exercise-templates' for listing or 'search-exercise-templates' for searching. No when-not or alternative guidance is provided.

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