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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the bar is lower — yet the description adds real semantics: an unmeasured axis is a 'first-class answer', 'never an error and never a zero', plus the 'Never a certification' disclaimer about what the data is not. That is genuine context an agent cannot get from the 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?

One dense, front-loaded sentence that opens with what the tool is and how to call it. The clause list of fields is long but each item earns its place; only the 'this tool IS the axis' phrasing is slightly redundant.

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 values needn't be spelled out, yet the description still names the key fields and — more importantly — explains how to interpret an unmeasured row. Complete for a no-arg, read-only axis lookup.

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 bundle is empty and additionalProperties=false, and the description confirms the tool takes no argument. It spends its words on return fields instead, which is appropriate for a no-arg tool.

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 the specific resource (the interop-conformance axis of the live GSPC board), gives its URL, and enumerates the row fields it surfaces. The framing 'this tool IS the axis' is a bit circular, and it never contrasts itself with close siblings like axis_conformance or axis_detector-interop, so an agent must infer the distinction.

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?

It states the call takes no argument, which is useful, but gives no when-to-use guidance: nothing says why to pick this axis over axis_conformance, axis_detector-interop, or get_axis. An agent gets no routing signal beyond the axis name.

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