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

Annotations already carry the read-only, idempotent, and non-destructive safety profile, so the description only needs to add value beyond that. It adds meaningful behavioral context: the tool is a live passthrough of the SqueezeOS endpoint and deliberately does not synthesize cluster-health or synchronization claims. No contradictions with 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?

Two sentences, with the core verb and resource front-loaded and a valuable caveat presented second. No wasted words or redundant restatement of the schema.

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 no-parameter, read-only status tool with rich annotations, the description is sufficient for an agent to call it correctly. It states what is read and what is not guaranteed, though it could have briefly noted expected response shape since no output schema exists.

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 and the schema coverage is effectively 100%, so there is nothing semantic to add. The description correctly implies that no arguments are needed, which is sufficient.

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 clear verb and resource: 'Read the live SqueezeOS status endpoint.' The negative caveat about not synthesizing cluster-health or synchronization claims adds scope precision, though it does not explicitly differentiate among sibling tools by 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 description implies when to use the tool — when you need raw, live status from the endpoint — and warns against expecting synthesized health/sync claims. However, it does not explicitly state when to prefer it over alternatives or provide exclusion criteria, leaving usage mostly inferred.

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