send_handoff_reminder

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

Annotations already flag readOnlyHint=false and idempotentHint=false, and the description usefully reinforces this with 'Sends a real email' and '(emails the team again)', signalling a real external side effect with no dedupe. It does not cover rate limits, who receives the email, or failure behavior, so it is not a 5.

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, front-loaded with the action and the precondition, and the terse 'Sends a real email.' earns its place by communicating the real-world side effect. 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?

For a 2-parameter mutation with no output schema, the description covers the precondition and the side effect but leaves agentId unexplained and says nothing about what a caller sees on success or failure. Annotations carry safety, so the gap is moderate rather than critical.

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 50%: userId is described in both schema and description, but agentId has no description in either place. The description adds disambiguation value for userId ('conversation / end-user id') but leaves agentId completely opaque.

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?

Specific verb+resource: re-sends the human-handoff notification for a conversation waiting on a human, with the parenthetical clarifying it emails the team. It is unambiguous and clearly distinct from the many CRUD siblings. It stops short of naming a sibling alternative, which keeps it at 4 rather than 5.

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 condition 'for a conversation that is waiting for a human' implies when to use it, but there is no explicit when-not guidance, no mention of when to prefer assign_conversation or send_channel_message, and no prerequisites or retry-throttling advice. Usage is inferred rather than stated.

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