Sender → Tasks

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

The description indicates mutation (creating reminders) but annotations set readOnlyHint: true and idempotentHint: true, creating a contradiction. The tool's behavior is not clearly disclosed.

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 a single truncated sentence, which is concise but incomplete. It lacks structure and does not fully convey the tool's purpose.

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?

The description is insufficient given no output schema. It does not explain what happens to emails after processing, the type of reminder created, or the return value of the 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 provides good descriptions for all three parameters (query, mailbox, limit). The tool description does not add any additional meaning beyond the schema, which is adequate given 100% coverage.

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 it scans mail for a keyword and creates reminders, which aligns with the tool name 'sender-to-tasks'. However, the description is truncated and could be more specific about the type of reminder.

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?

No guidance on when to use this tool versus alternatives like create_reminder or search_reminders. The description does not explain its unique value or 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.