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

With readOnlyHint already annotating the tool as a read operation, the description adds meaningful behavioral detail by specifying exactly what surfaces: unread threads, jobs waiting for action including payments due, and dispute cases waiting for a verdict. This clarifies the tool's aggregation behavior beyond the 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?

The description is a single, information-dense sentence that front-loads the tool's contents and ends with a direct usage directive. Every word earns its place; no filler or redundancy.

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 zero-parameter, read-only tool, the description is fully sufficient: it explains what the agent will see, when to call it, and implies no side effects. No output schema is present, but the tool's low complexity means the described contents are enough for correct invocation.

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 tool has zero parameters and the schema already provides complete coverage. There is nothing for the description to explain about parameter semantics, so the no-parameter baseline applies.

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 identifies the resource as an aggregate inbox of unread threads, actionable jobs, and dispute cases awaiting a verdict. It lacks an explicit verb such as 'list' or 'show,' but the title 'What needs my attention' and the enumerated contents make the tool's purpose unambiguous.

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 instruction 'Call this first in each session' gives explicit guidance on when to use the tool. It does not name alternative tools or exclusions, but the session-start placement is clear and actionable.

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