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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), but the description adds genuinely non-inferable semantics: an UNMEASURED axis is a first-class declared slot, 'never an error and never a zero', and the board is 'never a certification'. Those rules are exactly what an agent needs in order to interpret a null-looking result correctly.

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 front-loaded with the URL and the no-argument rule, which is good, but the middle sentence becomes a run-on field list (n, accuracy, interval, status, family, kind, URL, dates) that drifts into return-value detail. That enumeration partly duplicates what the output schema already declares and dilutes the two genuinely valuable statements.

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 fields needn't be spelled out — yet the description spends most of its length on them. What is missing is relational context: how this axis differs from get_axis, board_totals, or axis_provenance-controls, and whether the data is a live fetch or a cached board slice.

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 and the schema sets additionalProperties=false. No parameter meaning is left ambiguous.

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?

Names a specific resource (the provenance axis of the live GSPC board) and pins it to a concrete URL, which is more than the sibling axis_* names alone provide. However, it never states a verb ('returns the provenance axis row') and does not distinguish itself from sibling get_axis, which plausibly returns the same kind of data by name.

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?

The only usage-type guidance is 'it takes no argument', which is structural rather than situational. There is no statement of when to call this versus get_axis, axis_provenance-controls, or board_totals, and no exclusions or prerequisites.

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