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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds 'Free', a cost/licensing fact not present in annotations, but says nothing further about caching, versioning behavior, or response shape.

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 short sentences with zero waste; the core subject (methodology and version) is front-loaded and the operational caveat follows immediately. Nothing could be removed without losing information.

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?

For a read-only, no-argument reference lookup with no output schema, the description covers what is being returned (methodology text plus version) and its access characteristics. It does not state the response format, but that gap is minor for a tool this simple.

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, which is the baseline-4 case. The description correctly implies a parameterless lookup by describing a single fixed document, so no parameter explanation 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?

The description names a specific resource — the published Proof Score methodology plus its version — which is clearly distinct from the sibling tools proof_check, proof_index, and proof_verify_record. The verb is implied rather than stated ('returns'/'retrieves'), but an agent can tell this is a reference/documentation lookup rather than a data query or verification operation.

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?

'Free, read-only' hints that it can be called without side effects or cost, implying it is safe to consult at any point. However, there is no explicit statement of when to fetch the methodology (e.g., before interpreting proof scores) or how it relates to proof_index/proof_check, leaving usage to inference.

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