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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description adds that it is free and anonymous with no auth, no account and no side effects, and warns that 'unknown means unverified' and that workflow references 'do not promise availability... or eligibility.' These are meaningful behavioral caveats the 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?

The core purpose and the when-to-use cue are front-loaded, which is good, but the body is a dense run-on of semicolon-joined caveats that reads more like legal boilerplate. Several clauses ('Workflow tool references do not promise availability...') are useful but packed without structure, costing scannability.

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 output schema exists, so return values need no explanation, and the description covers scope, non-goals, anonymity, and fidelity caveats ('finite registry is not the complete roadmap'). It is largely complete for a no-arg discovery tool, with only the slightly overloaded framing keeping it from a 5.

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, and with additionalProperties=false there is nothing to document. Baseline 4 applies; the schema coverage is 100% and no parameter guidance is needed.

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 purpose: a discovery/registry tool for 'scientific capability contracts and domain suggestions' and tells the agent to 'Start here before choosing or funding a quantum job.' This distinguishes it from authenticated capacity-listing siblings, though the leading phrase 'Free, anonymous API-owned scientific capability contracts' is jargon-heavy.

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?

Explicitly says when to use it ('Start here before choosing or funding a quantum job') and delineates what it does not cover, noting that 'Existing authenticated tools own those operations' for accounts, quotes, reservations and execution. It names categories of alternatives rather than exact sibling tools, so it stops 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.