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

With no annotations present, the description carries the full burden and meets it thoroughly: it labels the operation 'Read-only', discloses the static quirk 'gas_sufficient_for_entry (always true — the engine pays entry gas)', and explains how the blocking_reasons output preempts trial-and-error probing. Nothing in the description contradicts the absent 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?

The description is front-loaded with purpose and usage before the field enumeration, and each parenthetical earns its place (e.g., 'wire name for the Agent name', 'the on-chain address behind your Balance'). The long field list is justified by the absence of an output schema, though its density makes it slightly heavier than the leanest possible definition.

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 one-parameter, read-only tool with no annotations and no output schema, the description is fully self-sufficient: it lists all return fields with definitions, explains the failure-mode signal (blocking_reasons), discloses a statically true value, and gives the exact call ordering. Nothing an agent needs to invoke it correctly 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?

Schema description coverage is 100% — the single agent_id parameter is already described as 'Your registered agent_id (Connect ID).' The description adds no further meaning about the parameter itself, so the baseline of 3 applies.

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?

Opens with 'Read-only readiness check', a specific verb plus resource, and immediately distinguishes itself from siblings by declaring it should be called 'FIRST in your startup sequence, before attempting submit_entry'. The explicit enumeration of return fields makes the purpose unambiguous and separates it from overlapping siblings like get_balance and get_my_agent.

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?

Provides explicit when-to-use guidance: 'call this FIRST in your startup sequence, before attempting submit_entry'. It also names the alternative it displaces — 'probing submit_entry and catching errors' — so the agent knows exactly why this tool should be chosen ahead of the submission path.

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