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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which the description does not contradict. The description adds that it returns balance and recent transactions, which is useful output context. However, it does not disclose additional behavioral traits such as supported chains, pagination, or error handling. Given the strong annotation coverage, a score of 3 is appropriate.

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 phrase, 'Address dashboard (balance + recent txs).' It is extremely concise with no filler words. Every word contributes meaning, making it appropriately sized and front-loaded.

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?

The description states the core function and output, and an output schema exists, so return values are covered elsewhere. However, it lacks usage context, supported chains, and parameter format details. For a simple two-parameter tool with strong annotations, this is adequate but not complete. The 0% schema coverage and lack of guidance prevent a higher score.

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 0%, and the description does not mention either parameter (chain, address) or their expected formats. The parameter names are self-explanatory, but the description fails to add any meaning beyond the schema, which itself lacks descriptions. This is a significant gap that the description does not compensate for.

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 'Address dashboard (balance + recent txs)' clearly indicates this tool retrieves a dashboard view for an address, including balance and recent transactions. It distinguishes from sibling tools like 'block' and 'transaction' by focusing on the address resource. However, it lacks an explicit action verb like 'fetch' or 'get', making it slightly less precise.

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 provides no guidance on when to use this tool versus alternatives. The sibling list includes related tools such as 'block', 'transaction', and 'entity_profile', but no exclusions or preferred contexts are mentioned. The word 'dashboard' implies a summary view, but that is not enough to guide selection.

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