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

Annotations already cover read-only, idempotent and non-destructive, but the description adds genuinely non-obvious behavior: an UNMEASURED axis is a first-class declared slot, never an error and never a zero, and the result is never a certification. That is exactly the kind of edge-case disclosure that prevents an agent from misreading a null result as failure.

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 identity and the no-argument fact are front-loaded, and every clause carries content. The one long enumeration of returned fields is slightly list-heavy for a description whose tool already has an output schema.

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 zero-argument, read-only, output-schema-backed tool, this covers what it is, where it lives, the empty-result semantics and the non-certification caveat. Nothing an agent needs in order to call it or interpret the response is absent.

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; the description reinforces this by stating the tool takes no argument. No further parameter semantics are needed or possible.

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 resource — the interpretability-reproducibility axis of the live GSPC board — and points to the hosting URL, so the agent knows exactly what entity it is fetching. It does not, however, differentiate itself from the ~30 sibling axis_* tools or from get_axis, which an agent seeing the tool list would need.

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 explicit when-to-use or when-not guidance, and no mention of the obvious alternative (get_axis, board_totals, measurement_index). The only routing help is 'it takes no argument', which tells the agent how to call it, not when to prefer it.

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