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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: returned bodies contain literal `{name}`, `{number}`, `{site}`/`{product}` placeholders the agent must substitute itself, and some replies are `paused` and out of plan. That is more than the annotations convey.

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?

Three short sentences, each carrying distinct information: what is returned, what the placeholders mean and who fills them, and what `paused` signals. The critical placeholder instruction is front and center with no filler.

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?

With no output schema, the description does the job of describing the return shape (title plus words) and the placeholder/caveat semantics. It omits ordering, pagination, or whether an empty result is possible, but for a zero-parameter read tool it is close to complete.

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 tool takes zero parameters, so there is nothing for the description to compensate for; baseline is 4. The description correctly adds no parameter narrative, which is appropriate here.

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 concretely: saved replies the team reuses, each carrying a title and a body. It is clearly distinct from siblings like list_articles or list_teammates, though the listing verb itself is only implied by the name/title rather than stated in the description.

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 does route the agent toward reply_to_ticket for actually sending and warns that `paused` replies are unavailable, which is useful operational context. However, it never states when to reach for this tool versus alternatives, or any prerequisites, so the guidance is implied rather than explicit.

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