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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile needs no restating. The description adds genuinely non-obvious behavior: an unmeasured axis is a first-class declared slot, published deliberately, never an error and never a zero, and is never a certification — exactly the ambiguity an agent would otherwise mishandle.

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 resource and URL, then the no-argument fact, then the unmeasured semantics. Slightly dense as one long clause-laden sentence, and the trailing 'Never a certification' fragment reads as an afterthought, but no sentence is wasted.

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 description need not explain return values, yet it helpfully sketches the row's fields and the unmeasured case. The only real gap is relational context — how this axis relates to axis_conformance and to the get_axis/board_totals family.

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, so the baseline is 4. The description reinforces this by stating the tool IS the axis and takes no argument, eliminating any doubt about whether a name or ID must be supplied.

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 names a specific resource (the machinery-conformity axis of the live GSPC board at an explicit URL) and enumerates what a row carries: n, accuracy, interval, measured/unmeasured status, family, kind, source URL and dates. The purpose is unmistakable, but it never says how this differs from the many sibling axis_* tools or from get_axis/axis_conformance, so sibling differentiation is absent.

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?

Usage is only implied: an agent infers it should call this to read the machinery-conformity axis, and the description does clarify that it takes no argument. There is no explicit when-to-use/when-not guidance and no pointer to axis_conformance or get_axis as alternatives, which matters given ~30 sibling axis tools.

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