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

With no annotations, the description carries full burden. It correctly states the tool returns balance, tx count, and token holdings, implying a read-only, non-destructive operation. However, it doesn't mention potential errors, rate limits, or whether it works for all address types (e.g., contracts).

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?

Single sentence with 10 words, no fluff. Gets straight to the point without unnecessary elaboration.

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?

Given no output schema, the description adequately indicates what will be returned. It covers the main data aspects but lacks detail on output format, potential errors, or specific edge cases. Still sufficient for an agent to invoke it correctly.

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 coverage is 100% and the parameter 'address' is simple. The description adds no extra meaning to the parameter beyond what the schema provides ('Flare address'). Baseline 3 is appropriate as the schema already documents it.

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 verb and resource: 'Address details on Flare' with specific data points (FLR balance, tx count, token holdings). It distinguishes from sibling tools like flr_token_search which searches tokens, and flr_network_stats which gives network-level data.

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?

No explicit guidance on when to use vs alternatives. The description implies use for address-specific queries, but doesn't mention when not to use it or point to siblings like flr_compliance_screen or flr_contract_check for other address-related tasks.

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