get_template

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

With no annotations, the description carries full burden for behavioral disclosure. It states 'Get details' but does not explain the nature of the details, any read-only behavior, or potential limitations. There is no mention of response structure, authentication needs, or side effects.

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, efficient sentence that immediately conveys the tool's purpose. Every word is meaningful, and there is no extraneous information. It is well front-loaded with the action and resource.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is minimally adequate but lacks detail on what 'details' are returned. For a complete understanding, the description could list example fields like name, content, or creation date. Without output schema, more completeness would improve agent confidence.

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% for the single parameter, with template_id described as 'The template ID'. The description adds no additional meaning beyond this, so baseline score of 3 is appropriate. No extra context is provided about the parameter's format or source.

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 verb 'Get' and the resource 'details for an email template', making the tool's purpose unambiguous. It distinguishes itself from sibling tools like copy_template, create_template, delete_template, update_template, and list_templates by specifying retrieval of details rather than copying, creating, deleting, updating, or listing.

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 offers no guidance on when to use this tool compared to alternatives. For instance, it doesn't explain that it differs from list_templates (which lists all templates) or that it requires a template_id. The context of use is implied but not explicit.

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