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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds important behavioral context: an unmeasured axis is a first-class answer (not an error or zero), the gap is published visibly, and the result is 'never a certification.' These are meaningful traits beyond 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?

The description front-loads the resource and URL, then explains the no-argument nature and returned fields, followed by behavioral notes. It is a single paragraph with dashes and is reasonably efficient, though slightly dense and could be structured more clearly.

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?

Given the tool's simplicity (read-only, no parameters) and the presence of an output schema, the description covers what is needed: it identifies the axis, lists the fields, and explains the unmeasured-status behavior. It does not detail how to interpret the returned measures, but the output schema likely handles structure.

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 takes no parameters, so there is nothing to document. The description redundantly states it 'takes no argument,' which is harmless but adds no value over the empty schema. Baseline 4 is appropriate for a zero-parameter 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?

The description identifies the resource as 'the art5-safeguard axis of the live GSPC board' and lists the data fields it exposes, but it does not use a clear action verb (e.g., 'return' or 'fetch') and does not distinguish this tool from the sibling get_axis or other axis_* tools. The agent can infer it retrieves axis data, but the purpose is not crisply stated.

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 offers no guidance on when to use this tool versus alternatives like get_axis, board_totals, or other axis endpoints. It explains that the tool 'takes no argument' but says nothing about choosing this specific axis or the conditions under which it should be called.

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