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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower, and the description adds genuinely useful context: it is paid per server, it 'reads the map only' (no server-side mutation), and it explains the per-tool result categories including risk rises. It does not describe failure modes or what happens if the lock is stale.

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?

Dense but front-loaded: the purpose and the lock input appear first, followed by the output categories, the rationale (rug pulls), pricing, and the read-only guarantee. No sentence is wasted, though the run-on structure packs several ideas into one long 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?

With no output schema, the description compensates by enumerating the per-tool result states (unchanged, changed with risk rise, removed, new) and the cost/auth model is covered in the schema. For a nested-object, 4-parameter tool this is nearly complete, missing only edge-case behavior for malformed or partial locks.

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 each parameter carries its own description, so the schema does the heavy lifting. The description adds provenance for the lock object (tool name to hash, as returned by watch or tool_card) but says nothing about server, last_trip, or license_key beyond what the schema already documents.

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 (verify/check) and resource (an MCP server's pinned tool list) and explicitly frames it as a lockfile comparison against a previously approved state. It differentiates itself from siblings by naming watch and tool_card as the sources of the lock and list_paid_tools for pricing.

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?

Gives a clear trigger scenario (confirming tools are still the ones a person approved, catching rug pulls after approval) and points to the siblings that produce the lock input. It does not spell out a when-not-to-use case or an alternative verifier, so it falls just short of a 5.

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