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

Annotations already declare it read-only, non-destructive, and closed-world, so the safety profile is fully covered structurally. The description adds only that the payload is 'machine-readable form', which hints at the return shape but says nothing about size, caching, or auth. With annotations carrying the safety burden, this is adequate but thin.

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?

A single short sentence with the endpoint path front-loaded followed by the payload meaning. Nothing is redundant or padded.

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 no output schema and no parameters, the description is the only place an agent can learn what comes back, and 'what Graunt offers to an agent, in machine-readable form' only gestures at it. It is enough to call the tool safely but not enough to know what to expect in the response.

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 zero parameters, so the baseline is 4 and there are no parameter semantics the description could have clarified or omitted.

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 endpoint (GET /v1/meta/capabilities) and says it returns what the service offers an agent, which is a real verb+resource. However, 'what Graunt offers' is vague about content, and it does not distinguish this from siblings like get_agent_commerce_manifest or meta_refinery_support_matrix, which plausibly overlap as capability/manifest reads.

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?

There is no statement of when to call this versus the manifest or support-matrix tools, and no exclusions. An agent must guess whether to start here for discovery or go straight to a more specific manifest tool.

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