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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description does add one non-trivial trait beyond the annotations: individual checks can be unavailable and must be surfaced explicitly, signalling partial results. It does not describe aggregation scope, result shape, or ordering, so the added context is real but thin.

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?

Two sentences, zero filler. The enumeration of what the queue contains is front-loaded, and the reporting directive follows as a short operational note. Every clause maps to a distinct concern.

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?

With no output schema, the description carries the burden of conveying what comes back, and listing the four queue categories largely does that. What remains missing is the shape of the response — counts vs. items vs. grouped sections — and whether results are workspace-scoped, which matters for an aggregate triage 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 single parameter is an empty object with 0% schema description coverage, so effectively this tool takes no meaningful input. With no parameters to explain, the baseline of 4 applies and the description correctly avoids inventing parameter guidance.

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 gives a concrete verb ('Read') and enumerates the resource categories returned: failed/stalled documents, invoices needing review, pending approvals, held exports. This is far more specific than the title 'What needs attention'. However, it never distinguishes this aggregate queue from overlapping siblings such as get_review_queue or list_approval_requests.

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?

There is no statement of when to reach for this tool versus the many specific list/get tools that surface the same underlying items. The only directive, 'Report unavailable checks explicitly,' is about how to present results, not when to select this tool, so the agent must infer that this is the top-level triage entry point.

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