get_template_details

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

No annotations are provided, so the description must fully disclose behavior. It only states that it returns details and including all customizable variables. It does not mention whether the operation is safe/read-only, error behavior for invalid template_id, permission requirements, or rate limits. This is insufficient for a tool with no annotation support.

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 concise sentence that front-loads the verb and resource. It includes only necessary information, though it could be slightly more structured. No wasted words.

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-details tool with one parameter and no output schema, the description adequately states the purpose and what the output includes (customizable variables). However, it lacks details on other potential return fields, error conditions, or usage context. It meets minimal completeness for this complexity level.

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?

The input schema covers 100% of parameters and the parameter description 'Template ID from list_templates' already provides source context. The tool description does not add further meaning for the parameter beyond what the schema gives. Baseline score of 3 is appropriate.

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 (Get) and resource (template details) and mentions that it includes all customizable variables. It implicitly distinguishes from sibling list_templates by focusing on details of a single template rather than listing all. However, it does not explicitly differentiate from other siblings.

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 usage after list_templates to retrieve details of a specific template, but it provides no explicit guidance on when to use this tool versus alternatives like generate_from_template, nor does it mention prerequisites or exclusions.

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