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

Beyond the readOnly/idempotent annotations, the description supplies genuinely useful interpretation rules that annotations cannot: an UNMEASURED axis is a first-class declared slot, never an error and never a zero, and the output is 'never a certification.' That prevents two concrete agent misreads (treating UNMEASURED as failure, or as 0). It stops short of describing provenance freshness or whether the live board can drift between calls.

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 short and front-loads the resource identity, and every clause carries content — no filler. But the first sentence is a run-on chain of clauses joined by dashes and colons, with the key semantics (unmeasured-as-answer, not-a-certification) buried mid-sentence rather than given their own line.

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 zero parameters and an output schema present, the return values need not be explained, and the description still covers the endpoint, the field vocabulary, and the semantic caveats around UNMEASURED and certification. What is missing is where this sits in the larger board workflow — whether to pair it with board_totals or get_axis to assemble a full view.

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?

Zero parameters, so the baseline is 4, but the sentence 'takes no argument: n, accuracy, interval, MEASURED or UNMEASURED status...' presents output fields in the syntactic position of arguments, which can momentarily read as a parameter list. It is consistent with the schema (empty object, additionalProperties:false) yet adds a small ambiguity rather than clarity.

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?

It identifies the resource precisely ('the reserve-attestation axis of the live GSPC board') and pins the endpoint, but never states the action or what calling it yields — the reader has to infer from 'the row' and the field list that it returns one axis's record. Against ~35 sibling axis_* tools whose names alone carry the same amount of information, it does little to differentiate beyond topic.

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?

There is no guidance on when to call this versus get_axis, board_totals, measurement_index, or the other axis tools — all plausible alternatives for retrieving axis data. The only usage-adjacent statement ('takes no argument') is a constraint, not a selection rule.

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