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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds the cost ('free'), the L8-and-above gate on blast-radius data, per-part measurement times and definition ids, and an explicit interpretation caveat: 'Facts, never a verdict: a clean list does not mean safe.' That caveat matters because a clean result could otherwise be read as a safety verdict. It does not disclose truncation, pagination, or failure modes when a component cannot be checked.

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?

It is front-loaded with the audience and the free-call framing, which is good. But the core is one sprawling sentence packing six content areas plus parenthetical sub-clauses, and a reader must parse it linearly to extract the parts list. The density is earned by scope, but the structure could be a short lead plus a bulleted inventory at no cost in length.

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 correctly shouldered the burden of saying what comes back, and it does: the component list, the worth_a_look rollup with sources, and the per-part measurement time and definition id. It does not describe the envelope shape or how components that 'could not be checked' are represented, which is the one material gap for a composite 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?

Schema coverage is 100% with a single required parameter, and the schema description already spells out the accepted forms (token id act_8453_N, slug, or bound wallet). The description adds no format or resolution detail beyond that. Baseline 3 applies when the schema already carries the meaning.

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 concretely enumerates what the call returns about one agent: record and level, Agent Pass, the Watch reading of the newest payment, 30-day token approvals, 30-day detections, and L8+ blast radius. That is a specific verb-plus-resource statement an agent can act on. It stops short of naming any sibling tool, so the boundary against agent_record, agent_pass, or detections is only implied by the enumeration rather than stated.

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?

'One free call for an agent to check itself, or for the person who runs it' sketches the audience and the cost condition, which implies this is the entry-point survey. There is no explicit when-not guidance and no routing statement telling an agent to use this instead of, or before, the granular sibling tools it aggregates. Usage is inferable but not directed.

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