get_canned_response

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

No annotations are provided, so the description carries the full burden. It only states 'Get a specific canned response by ID' and does not disclose read-only behavior, failure modes, response format, or any side effects. This is minimal disclosure 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 very brief and to the point, consisting of one sentence and an Args list. However, the Args section redundantly repeats the schema information and could be integrated more cleanly. It is not overly verbose, but also provides minimal added value.

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 a get-by-ID operation with one parameter and an output schema, the description is minimally sufficient. However, it lacks any context about behavior on missing IDs, authorization, or differentiation from similar lookup tools, leaving gaps for a complete understanding.

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 schema has 0% description coverage and only provides the parameter name and type. The description adds 'The canned response ID,' which provides slight semantic clarification but largely restates the parameter name. No additional constraints or format details are given.

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 'canned response' identified by ID. It is specific about the operation, though it does not explicitly differentiate from sibling tools like get_ticket_by_id beyond naming the resource.

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisite conditions. It is implied that a response ID is needed, but no explicit context or exclusions are given.

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