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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds genuinely new context beyond that: values are read at the latest block, and no key or payment is required during launch. It does not describe pagination, caching, or the shape of the returned state object, which matters because there is no output schema.

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 tight sentences, front-loaded with the resource and the exact readouts, then a short note on access conditions. No filler or repeated title text.

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?

An 8-parameter tool with no output schema, so the description carries the burden of describing returns, and it does name the concrete readouts (isOperation/pending/ready/done, ETA timestamp, min delay). What it omits is the relationship between opId and the target/value/data derivation path, which is the main thing an agent could get wrong.

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% and every parameter carries a description, so the baseline is 3. The description adds the useful detail that results are resolved at the latest block and that the call is free of auth, but it says nothing extra about the opId-versus-target/value/data/predecessor/salt alternative paths; those are left entirely to the schema.

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?

Names a specific verb implied by 'scan' and a concrete resource: live OpenZeppelin TimelockController operation state, and enumerates what it reports (isOperation/Pending/Ready/Done, getTimestamp ETA, getMinDelay). It stops short of differentiating itself from the closest sibling pacta_get_live_timelocks or pacta_check_preflight.

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 never states when to reach for this tool versus pacta_get_live_timelocks, pacta_check_preflight, or pacta_scan_proposal_diff. An agent must infer that this is the per-operation status lookup rather than a listing or a preflight simulation from the word 'operation state' alone.

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