get_awaiting_reply

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

The description explains the operation: scanning Sent mailbox, cross-referencing Inbox, and returning results. It implies read-only behavior without destructive actions. However, it lacks explicit statements about read-only guarantees or authorization needs.

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 well-structured with a clear summary, detailed explanation, and separate sections for Args and Returns. It is concise and front-loaded, with every sentence adding value.

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 (4 parameters, output schema exists), the description covers all essential aspects: purpose, logic, parameters, and return format. No crucial information is omitted.

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?

With 0% schema description coverage, the description's Args section fully compensates by explaining each parameter's purpose, defaults, and meaning, providing critical semantic context beyond the schema.

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: 'Find sent emails that haven't received a reply yet.' It explains the cross-referencing logic and mentions follow-up tracking, making the function unambiguous and specific.

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?

While the description says 'Useful for follow-up tracking', it does not explicitly guide when to use this tool over alternatives like 'get_needs_response' or other email search tools. There is no mention of when not to use it.

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