get_template_info

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the specific-template scoping and is consistent with the tool's read-only nature. It does not disclose additional behavioral details, but the lower bar for annotations makes this adequate.

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 short, front-loaded with the purpose, and contains no filler. The Args line is slightly redundant with the input schema but does not significantly bloat the overall description.

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 one-parameter read-only tool with an output schema, the description is operationally mostly complete. However, it does not clarify which category of 'template' it refers to, especially given siblings like get_template_file_info and list_slide_templates. An agent could misroute without additional disambiguation.

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 carries the burden. It provides 'template_id: ID of the template to get information about,' which explains the parameter's role. This is minimal but sufficient for a single string ID, though it adds little beyond the schema title 'Template Id' and gives no format or lookup details.

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 states a clear verb and resource: 'Get detailed information about a specific template.' This is unambiguous about the basic operation. However, it does not distinguish itself from sibling tools like get_template_file_info, which could also plausibly return detailed template information.

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?

There is no when-to-use or when-not-to-use guidance. With siblings such as get_template_file_info, list_slide_templates, and get_presentation_info, an agent must infer the correct choice. The description only implicitly suggests a single-item lookup from a template.

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