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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that, the description adds genuine domain semantics: SLA counts are scoped to non-terminal issues, dependency blocks identify the blocking item, and a stale lastRenewedAt is interpreted as an unresewed claim running on bare TTL.

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?

Front-loaded with the verb-and-object, then a tight enumeration; every clause carries information. The nested parentheticals (especially the claim/lease explanation) make it dense, but no sentence is padding.

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 must itself convey what comes back, and it does: status counts, ready-to-pull totals, breaching/breached counts, dependency-blocked detail, and claimant/lease fields. An agent knows what to expect from the response without a schema.

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 takes zero parameters (100% schema coverage on an empty object), so per the rubric the baseline is 4. There is nothing further for the description to clarify about inputs.

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?

States a specific verb and resource — 'Diagnose the queue' — then enumerates the exact facets it reports (counts, ready-to-pull, SLA pressure, dependency blocks, active claims). This distinguishes it from siblings like list_issues, next_batch, and check_claim, which cover narrower slices of the same domain.

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?

Usage is implied: this is the broad diagnostic overview, so an agent can infer it is the right call before drilling into check_claim or list_issues. However, the description never explicitly says when to prefer it over those siblings, nor when not to use it, so the routing decision is left to inference.

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