ofw_get_unread_sent

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

Discloses key behaviors: reads from local cache, returns a 'complete' flag, and refusal with UNVERIFIED_EMPTY when cache is not fresh. Explains autoRefresh side effect, aligning with readOnlyHint=false annotation.

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?

Four-sentence paragraph is front-loaded with purpose, every sentence adds value, no wasted words.

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?

Even without an output schema, the description explains the 'complete' return field and special refusal result. All necessary details for using the tool are present.

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%, and the description adds significant context for autoRefresh, including default behavior and cost implications, exceeding raw schema descriptions.

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?

Clearly states the tool lists sent messages that are unread by recipients, with specific verb and resource. Distinguishes from sibling tools like ofw_list_messages by specifying unread sent messages and local cache usage.

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?

Provides guidance on using autoRefresh to avoid refusal, explaining when it's needed. Does not explicitly contrast with alternatives, but the tool name and context imply its specific use case.

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