triage_email

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

No annotations are provided, and the description does not clarify whether this tool has side effects (e.g., modifies email state) or if it is a read-only operation. It also does not mention any required permissions or potential impacts.

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 description is brief and to the point, using a single sentence to convey the core functionality. It is appropriately concise, though it could benefit from a bit more detail.

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?

Given the tool's complexity (classification and suggestion), the description lacks necessary context such as input requirements, output format, or how the reply suggestion is generated. It does not provide enough information for an agent to use it effectively without additional assumptions.

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 schema provides no descriptions for the five parameters (id, sender, subject, body, senderName), and the description does not explain their meaning or usage. Parameter semantics are entirely unspecified.

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 clearly states the action ('classify') and the resource ('an email'), and specifies the outputs: urgency, category, and reply suggestion. However, it does not distinguish this tool from sibling tools like search_emails or get_recent_emails, which also operate on emails.

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 description implies a use case (classification and reply suggestion) but does not explicitly state when to use this tool versus alternatives like search_emails or get_conversation_thread. No conditions or prerequisites are mentioned.

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