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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read. The description adds valuable context: a limit of 50 tasks and a warning that task contents are untrusted counterparty data. This goes beyond the annotation and helps the agent handle the data appropriately.

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 two sentences with no waste. The primary action and scope are front-loaded, and the security caveat is appended without clutter. Every sentence earns its place.

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?

For a tool with no parameters, an output schema (indicated by signal), and read-only annotations, the description covers everything needed: what it reads, how many, and the nature of the data. Nothing critical is missing.

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?

There are zero parameters, so the description needs no parameter documentation. Baseline for 0 params is 4; the description adds no redundant parameter info and stays accurate.

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 reads offered or accepted tasks addressed to the mailbox, with a specific resource ('tasks') and scope ('up to 50', 'offered or accepted'). It is distinct from siblings like get_task (specific task) and get_mailbox (mailbox settings), so an agent can identify its purpose without ambiguity.

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 this is for reading multiple tasks from the mailbox, but it does not explicitly state when to use it versus alternatives like get_task or get_mailbox, nor does it mention conditions or exclusions. The context is clear but not explicit about routing.

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