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 bar is lower; the description still adds useful context by disclosing that the payload is sanitized and that it reflects origin liveness and fee-route configuration. With no output schema, this is helpful but still thin on what specific fields come back.

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?

Three short sentences, purpose front-loaded, and the final negative clause earns its place by preventing confusion with the many per-token/token siblings. No filler.

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, low-complexity health check with no output schema, the description covers what is being verified and that the response is sanitized. It could be slightly more explicit about how an agent should act on a failure, but it is adequate for correct invocation.

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 per the rubric the baseline is 4 and no compensating parameter documentation is needed. Nothing is ambiguous about the (empty) input.

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 (health/readiness of the origin) and clarifies the check's scope: origin up plus fee-route configuration. The closing "Not per-token data" distinguishes it from per-token siblings like memeswap_token/memeswap_tokens, though the verb phrase "Sanitized readiness" is slightly abstract.

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?

It says what the tool is not (per-token data) but gives no positive guidance on when an agent should call it versus alternatives, nor any prerequisites or failure conditions. Usage must be inferred from the name and the name of the endpoint.

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