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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description adds semantics beyond them: an unmeasured axis is a declared slot with no run behind it, 'never an error and never a zero,' and the result is 'never a certification.' That prevents concrete misreadings of the payload. It does not mention rate limits, caching, or freshness beyond 'live'.

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 identity and scope, then the field inventory, then the interpretation caveat. Dense but every clause carries information; the only redundancy is restating the axis/title phrasing twice in the opening sentence.

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 need not be explained, and the description is adequate for calling the tool. What it omits is the sibling landscape: with ~35 axis_* tools plus get_axis, the agent has no basis for choosing this one over axis_humanoid-labour-index or the generic axis reader.

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 is consistent with the empty schema, explicitly saying the tool takes no argument, which reinforces that the agent should not invent filters.

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?

States a specific resource — 'the humanoid-deployment axis of the live GSPC board' — and enumerates what the axis carries (n, accuracy, interval, MEASURED/UNMEASURED status, family, kind, artifact URL, dates). It also clarifies the tool is the axis itself rather than a lookup, which implicitly separates it from argument-taking readers. However, it never distinguishes itself from the very similar sibling axis_humanoid-labour-index or from get_axis, so an agent must guess which of the near-identical names to pick.

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?

'This tool IS the axis, so it takes no argument' conveys usage implicitly: call it directly to read this axis. The unmeasured-is-a-first-class-answer sentence also warns against treating a gap as failure. But there is no explicit when-to-use/when-not guidance versus get_axis or axis_humanoid-labour-index, so routing between siblings is left to inference.

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