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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value beyond them by disclosing the return payload shape (services[] {name, ok, detail} plus an overall ok flag), which matters because no output schema exists. It stops short of noting rate limits, caching/freshness of 'live' data, or failure behavior when the gateway itself is unreachable.

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 dense sentences, all front-loaded: identity first, then when-to-use, then when-not-to-use with alternatives, then the return contract. No filler, no restatement of the title.

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 zero-parameter health-check tool with no output schema, the description supplies everything needed to select and call it: scope, routing rules, and the returned field structure including the overall ok flag. Nothing an agent needs is missing.

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 and the schema is empty, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The stated return fields are not parameters and correctly do not substitute for parameter documentation.

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 ('live availability of every service behind the RobotBase gateway') and enumerates the services covered (chain nodes, Web3 Agent Hub, AITOKENS, MCP). It also names the two siblings it is not (chain_status, robotbase_capabilities), so the agent can distinguish it without opening any schema.

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?

Explicit 'When to use' (overall platform health check, finding which service is down) and explicit 'Do not use' routing to chain_status for single-chain node state and robotbase_capabilities for capability boundaries. Both conditions and alternatives are stated, leaving nothing to inference.

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