manage_canned_response

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only lists actions and parameter requirements, without addressing whether operations are read-only, require special permissions, or have side effects. This is a significant gap for a tool named 'manage'.

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 minimal and well-structured, with a summary line and a clean Args block. Every line contributes necessary information without waste or redundancy.

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?

The description covers basic actions and parameter requirements but lacks context on operation semantics, return behavior, or edge cases. The presence of an output schema reduces the need to describe returns, but the description still leaves behavioral questions unanswered.

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 description compensates for the schema's lack of descriptions by explicitly stating that response_id is required for 'get' and folder_id for 'get_folder', providing conditional requirements not evident from the schema. It also enumerates the valid action values, adding essential meaning beyond the schema structure.

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 identifies the resource (canned responses) and lists specific actions (list, get, list_folders, get_folder), making its purpose clear. However, the verb 'manage' is generic and does not differentiate from many sibling manage_* tools beyond the resource name.

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 explicit guidance on when to use this tool versus alternatives, nor any exclusions or conditions. The listed actions imply certain use cases, but there is no mention of when not to use it or which sibling tool might be more appropriate for other operations.

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