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 only states the output fields (balance, tx count) and implies a read-only, non-destructive query. It does not disclose limitations, address format requirements (e.g., bech32 vs legacy), network (mainnet/testnet), or potential failure modes, leaving the agent to infer critical operational details.

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 short sentence that front-loads the core purpose. There is slight redundancy with the title ('LTC Address' vs 'Litecoin address'), but overall it is appropriately sized and contains no filler 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?

Given the simplicity of the tool, the description is still incomplete. It fails to document the parameter 'q', leaves address format and network assumptions ambiguous, and provides no usage context. Although an output schema exists, the lack of parameter documentation and behavioral details makes the description insufficient for correct invocation without external knowledge.

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 schema for the only parameter 'q' has 0% description coverage, and the description never mentions 'q' or explains how the address should be formatted. The only hint is the tool's purpose, which implies q is the Litecoin address, but the description does not explicitly map or define the parameter, forcing the agent to make assumptions.

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 identifies the resource (a Litecoin address) and the data returned (balance and transaction count), making its purpose distinct from sibling tools like btcaddr or dogeaddr. It lacks an explicit verb (e.g., 'get', 'lookup'), but the phrase 'Litecoin address balance & tx count' effectively states the function.

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 is given on when to use this tool versus alternatives, nor any exclusions. However, the description implies the usage context: querying Litecoin address data. This is sufficient for a tool whose name and description already narrow the domain, but it does not name sibling tools or provide decision criteria.

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