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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the shape of the returned items (id, topic, assignee), which matters because no output schema exists. It still omits volume, pagination, and scope behavior.

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?

A single front-loaded sentence that identifies the resource first and then its returned fields; no filler. The relative clause 'who takes over a conversation the assistant hands to a human' is slightly heavy but does real explanatory work and earns its place.

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 one-parameter list tool with annotations covering safety, the description covers the resource, its meaning, and the return fields, which is what an output-schema-less tool most needs. Minor gaps remain around result volume or pagination, but nothing required to call it correctly 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% for the single workspaceId parameter, which already documents the default-to-connection-workspace behavior. The description adds no parameter-level meaning, so the baseline of 3 applies.

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 names a specific resource (handoff routing rules) and explains what they govern — who takes over a conversation handed to a human — plus the fields returned (id, topic, assignee). That clearly separates it from create_routing_rule, update_routing_rule, and delete_routing_rule, though it never states the verb 'list' explicitly and relies on the name to convey the read operation.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that this is the read counterpart to create/update/delete_routing_rule; nothing in the text routes it between siblings or describes prerequisites.

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