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

Annotations only cover the safety profile (not read-only, not idempotent, not destructive). The description goes further: it explains that the AI classifies into topics, that only a well-written topic description makes classification work, and that unassigned rules are silently ignored. That is genuine operational context beyond the annotations.

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 paragraph that opens with the core action, then the mechanism, then the caveat. Dense but every sentence carries information; nothing is 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?

For a mutation tool with no output schema, the description covers the action, the classification behavior, the assignee requirement, and points at list_team for valid IDs. The idempotency behavior is handled in the schema, so little 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 coverage is 100%, so the baseline is 3, but the description adds meaning by tying assignUserId/assignTeamId to list_team as the source and by stressing that the topic description drives classification quality. This is light but real value on top of the schema's own parameter docs.

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 states a specific verb and resource: adding a topic and its assignee for automatic handoff routing, and even explains the classification mechanism. It is clearly separable from siblings like update_routing_rule, delete_routing_rule, and list_routing_rules, though it never names them explicitly.

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 gives the scenario context ('when a handoff is set to assign automatically') and notes that a rule with no assignee is ignored, which implies a prerequisite. However, it never states when to reach for this tool over update_routing_rule or list_routing_rules, leaving the when-to-use choice implied.

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