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

With annotations present, the description still adds substantial behavioral context beyond them: unit price (0.25 USDC on Base), a quota (10 signed-wallet free calls per rolling 30 days), the required credential/mandate/action-grant context, and an explicit negative boundary (no provider work, callbacks, document retrieval or attestations). Quota, cost, and auth disclosure are exactly the traits annotations do not convey.

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?

Pricing and access terms are front-loaded ahead of the actual purpose, and several claims are repeated ('grants no authority', 'bounded computation on caller-supplied data', 'uses supplied data only'). The content is relevant but the ordering and redundancy dilute a tool whose core function is one sentence.

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?

There is no output schema, so the description should carry return-value meaning; it is fair on this point by specifying 'deterministic priorities' and reiterating that no activity is invented. Combined with full schema coverage and rich access/auth detail, an agent has enough to call it correctly, though the output shape remains only loosely described.

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?

Schema description coverage is 100%, so the schema already documents as_of, services, and queues and their constraints. The description only restates the input domain ('service health and queue observations') without adding syntax or format meaning, so the baseline 3 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 second sentence states a specific verb and resource: 'Summarize supplied service health and queue observations into deterministic priorities.' That is clear enough to identify the operation. However, it is buried behind pricing and access text, and no sibling among the 24 is named to distinguish it directly.

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 gives access-path guidance (x402 USDC vs. verified-wallet free tier vs. free /api/mcp or /api/service-resolver) and an operating boundary, which implies usage. But it never states when to choose this tool over the many sibling rails (e.g., sla-rail, budget-guard, trust-scorecard), so routing guidance is only inferred.

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