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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: an unmeasured axis is a declared slot with no run behind it, is 'never an error and never a zero', and results are 'never a certification'. That materially shapes how an agent should interpret empty-looking output.

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?

Front-loaded with the resource identity, but the phrase 'takes no argument: n, accuracy, interval, ...' is structurally confusing — it reads as if those were arguments before it becomes clear they are returned fields. The field enumeration duplicates what the output schema already provides.

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, and annotations cover safety. What remains missing is the meaning of 'continuity' as a measured dimension and how this axis relates to the sibling axis tools and board_totals — the agent still cannot reason about when this axis is the right one.

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 correctly reinforces that no arguments are accepted, which is consistent with the empty schema with additionalProperties=false.

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 a specific resource ('the continuity axis of the live GSPC board') and gives its source URL, so the agent knows it is fetching one axis of one board. But 'axis' and 'continuity' are unexplained jargon, and with 30+ sibling axis_* tools the description never says what distinguishes continuity from affect, safety, provenance, etc. The 'this tool IS the axis' framing partly restates the 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 guidance is negative ('takes no argument'). It never says when to reach for this versus get_axis, board_totals, measurement_index, or get_card, all of which appear to surface overlapping board data. The one useful rule — an UNMEASURED axis is a valid answer — is semantic, not routing guidance.

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