admin_list_canned_responses

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

Without annotations, the description should disclose behavioral traits. It only states the action, failing to mention whether the operation is read-only, requires authentication, or returns paginated results. The lack of annotations and minimal description leaves the agent without crucial behavioral context.

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 short (4 words) and lacks structure. While it is concise, it does not front-load key information or provide any additional context beyond the bare minimum. It is acceptable but not well-structured.

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 tool has no parameters and no output schema, the description is minimal. It does not explain what a 'canned response' is, what fields will be returned, or any limits. For a list operation, more detail (e.g., 'Returns all canned responses with their IDs and names') would improve completeness.

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?

There are no parameters, and the schema coverage is 100% (empty schema). The description does not add any parameter semantics, but none are needed. The baseline of 3 is appropriate as the schema already fully documents the lack of parameters.

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 'List canned ticket responses' clearly identifies the action (list) and the resource (canned ticket responses), making it easy to understand the tool's purpose. It is not a tautology and is specific enough to differentiate from unrelated tools.

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?

No guidance is provided on when to use this tool versus alternatives like admin_create_canned_response or other list tools. There is no context about intended use cases or situations where this tool might be inappropriate.

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