get_needs_response

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

With no annotations, the description provides substantial behavioral details: it filters out newsletters and automated emails, prioritizes direct emails with question marks, and returns a ranked list with priority hints. This adequately informs the agent about the tool's behavior, though it does not explicitly state read-only nature.

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 concise and well-structured: a brief purpose paragraph followed by a clear Args listing. No superfluous information, though the purpose statement could be slightly more front-loaded.

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 presence of an output schema (not shown but referenced), the description appropriately summarizes the return type. It covers the filtering logic and all parameters. Minor gap: no mention of whether emails are marked as read, but overall sufficient for a retrieval tool.

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 input schema has 0% description coverage, but the description compensates fully with a clear 'Args' section explaining each parameter's purpose and defaults (e.g., account as the email account name, mailbox defaulting to 'INBOX'). This adds significant meaning beyond the schema structure.

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 tool's purpose: identifying unread emails that likely need a response. It specifies filtering and prioritization criteria, making the action clear. However, it does not differentiate from sibling tools like 'get_awaiting_reply', which may have overlapping functionality.

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 when to use (when you need to find actionable emails), but it lacks explicit guidance on when not to use this tool or which alternatives to consider. No mention of siblings or exclusions, leaving the agent to infer usage context.

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