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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds the cost detail 'Free' and describes the action as a 'connectivity check,' which implies a read-only operation. However, it does not explicitly state that the operation is safe, has no side effects, or what it returns. For a simple health probe, this is adequate but not fully transparent.

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 that is front-loaded with the core purpose ('RPC connectivity check'), followed by two high-value extras: cost ('Free') and usage guidance. Every word earns its place, with no redundancy or filler. It is a model of conciseness.

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 tool with no parameters and no output schema, the description covers the essential aspects: what it does, when to use it, and cost. It does not specify the return format or how to interpret results, but for a simple connectivity check, the agent can infer that it returns a status. The description is largely complete for the tool's simplicity.

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 input schema is trivially complete at 100% coverage. The description does not need to explain parameter details, as there are none. According to the rubric, 0 parameters yields a baseline of 4, which is appropriate here.

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 clearly states the tool's function: 'RPC connectivity check.' This is a specific verb (check) and resource (RPC connectivity), and it distinguishes the tool from siblings like inspect_wallet or payment_info, which serve different purposes. The phrase is unambiguous and directly conveys what the tool does.

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 gives explicit usage context: 'Use when diagnosing timeouts before paid calls.' This tells the agent when to invoke the tool (when timeouts are suspected) and provides a temporal reason (before spending on paid calls). It does not explicitly name alternative tools or state when not to use it, but the context is clear and sufficient for decision-making.

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