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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: zero arguments by design, the field set surfaced, the rule that an unmeasured slot is a published gap rather than an error or a zero, and the 'never a certification' disclaimer against over-reading the result.

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?

Three sentences, front-loaded with the identity and URL, then the zero-argument rule, then the unmeasured semantics, then the disclaimer. Dense but each clause carries information; the em-dash parentheticals in the middle sentence are the only mild wordiness.

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 and annotations are rich, so return-format and safety detail are not required here. What is missing is routing context: with 34 sibling axis_* tools including axis_regulator-transparency, the description should say how this axis differs or how to enumerate the others. Otherwise it is adequate for a zero-argument read.

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 and 100% schema coverage, so the baseline is 4. The description goes slightly further by explaining that the absence of arguments is intentional ('this tool IS the axis'), which preempts an agent hunting for a filter or axis-id parameter.

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 names the resource precisely — the regulatory-framework axis of the live GSPC board — and points to a concrete URL. But it never states the operation plainly ('this tool IS the axis' is a riddle where 'returns the current row for this axis' would do), and it doesn't distinguish itself from the near-identically named sibling axis_regulator-transparency or from get_axis.

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 statement of when to call this versus get_axis, board_totals, list_cards, or the 30+ sibling axis tools. The only usage-shaped guidance is interpretive ('an unmeasured axis is a first-class answer — never an error and never a zero'), which tells the agent how to read the result but not when to reach for this tool.

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