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

With annotations already declaring readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, the description adds meaningful behavioral context: an unmeasured axis is published as a first-class declared slot, never an error and never a zero. It also warns 'Never a certification,' which is useful interpretation guidance beyond the structured annotations.

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 description front-loads the core resource and no-argument constraint, then explains the unmeasured status semantics. The long em-dash sentence listing fields is somewhat run-on and partly redundant with the output schema, but overall the text is appropriately sized and every sentence contributes context.

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?

Because an output schema exists, the description does not need to explain the return shape in detail. It covers the important zero-parameter behavior and the special unmeasured-axis semantics, though it is less complete on how this axis tool relates to sibling axis readers and get_axis.

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 has zero parameters, and the description explicitly reinforces that it takes no argument. That is a small but helpful confirmation beyond the empty schema. The baseline for zero-param tools is 4, and no parameter-semantics gap remains.

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 identifies a specific resource, the regulator-transparency axis on the live GSPC board, and says it takes no arguments. However, it never states the action in a clean verb like 'returns' or 'fetches', relying on 'this tool IS the axis' to imply retrieval. It also does not distinguish this zero-argument axis tool from siblings such as axis_* tools or 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?

The description establishes that the tool takes no arguments and explains that an unmeasured axis is a valid answer, which implies this is a direct lookup of one specific axis. It gives no explicit guidance on when to use this tool instead of get_axis or the many other axis_* siblings, nor does it state prerequisites or exclusions.

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