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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description's burden is lower. It adds value by emphasizing that the endpoint is 'live' and by cautioning that the tool does not synthesize health claims, which is useful behavioral context beyond the structured hints.

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 is a single sentence with no wasted words. It front-loads the verb and resource, and the clarifying negation earns its place by preventing a likely misuse.

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?

For a parameterless, read-only, idempotent tool with rich annotations and no output schema, the description tells the agent everything needed to decide when to call it. The sibling context shows no overlapping tool, so the description is fully adequate.

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 has zero parameters, so the description cannot add parameter-level meaning. Per the baseline for tools with no parameters, a score of 4 is appropriate: there is nothing missing and the description correctly focuses on the operation itself.

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 verb ('Read') and resource ('live SqueezeOS status endpoint'), making the tool's function immediately clear. The added clause 'without synthesizing health claims' sharpens the purpose by stating what the tool does not do, which helps distinguish it from potential diagnosis or recommendation tools among the siblings.

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 implies the tool should be used when raw, live SqueezeOS status is needed, and the 'without synthesizing health claims' phrase signals that it is not for drawing health conclusions. It does not explicitly name alternative tools or exclusion conditions, but the sibling list (capability, x402, compare) makes the intended scope clear enough.

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