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

The description leads with 'Read-only', reinforcing annotations and telling the agent the call is safe. It adds that it reports the existential deposit and nonce, which goes beyond generic readOnly/destructive hints. It does not cover failure behavior for nonexistent addresses beyond 'whether an address exists'.

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?

One sentence, front-loaded with the read-only safety marker, then a compact enumeration of return fields. No wasted words.

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 simple single-parameter read tool with no output schema, the description lists the key return values, which is the main missing piece. It does not explain how a nonexistent address is represented, a minor gap.

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?

There is only one parameter, and the schema fully documents it (SS58 address). The description adds no format or validation details beyond the schema, so baseline 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?

States a specific resource (an address's on-chain state) and enumerates exactly what is returned: existence, free/reserved/frozen balance, existential deposit, nonce. No sibling tool overlaps this purpose.

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 usage (reading account state) but does not state when to use this versus related tools like geode_profile_get_account_profile or geode_messaging_get_account_settings_data, nor any prerequisites. Usage is inferable but not explicit.

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