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

The annotations already declare readOnlyHint=true, correctly signaling a safe read operation. The description adds only minor context (saved/canned replies, endpoint mapping) and does not disclose return format, pagination, or any rate-limit behavior beyond what annotations provide.

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 purpose and optional filter are front-loaded in a single efficient sentence, with the endpoint mapping appended as useful metadata. There is no redundant or filler language.

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 simple, read-only list tool with one optional enum parameter and no output schema, the description is nearly complete: it states what is listed, the optional filter, and a use case. It could mention pagination or result cardinality, but no critical information for correct invocation is missing.

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%, so the single 'type' parameter and its enum values are already fully documented. The description restates the optional filter in prose ('messaging or email ones') but adds no syntax or format detail beyond the schema.

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 gives a specific verb ('List'), resource ('saved quick replies (canned responses)'), optional filter scope, and maps to the underlying endpoint 'GET /quick_replies'. It clearly distinguishes this tool from the many other list operations by 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?

It provides a clear context ('useful for drafting consistent answers') but does not include explicit when-not conditions or alternatives. For a simple read-only list with no close sibling to disambiguate, this is adequate context without exclusions.

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