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 states the tool returns balance and tx count, which is useful, but it does not disclose whether the address must be valid, what happens for invalid addresses, whether it makes a network call, rate limits, or the response format. For a lookup tool with zero annotation coverage, this is a significant gap.

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 concise sentence that front-loads the resource ('DOGE Address') and the key outputs ('balance & tx count'). It is appropriately sized for a simple lookup tool, with no wasted words. It could be slightly improved by adding a verb, but it is efficient.

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 tool has one parameter, no annotations, and an output schema exists but is not shown in the input schema. The description is minimal and does not explain the expected input format, the output structure, or any edge cases. For a tool with zero schema description coverage and no annotations, the description is not complete enough for an agent to invoke it confidently without additional context.

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 only parameter 'q' has no description in the schema. The tool description says 'DOGE Address' which implies 'q' is a Dogecoin address, but it does not specify the expected format (e.g., base58, starting with 'D'), whether it accepts a URI-encoded address, or any validation rules. The description adds minimal meaning beyond the parameter name 'q'.

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 'DOGE Address: Dogecoin address balance & tx count' states a clear verb-less resource and the two data points it returns (balance and transaction count). It distinguishes itself from sibling tools like btcaddr, ethaddr, ltcaddr, soladdr, and xrpaddr by naming the specific cryptocurrency (Dogecoin), so an agent can tell it apart. However, it lacks an explicit verb like 'lookup' or 'query', making it slightly less direct than ideal.

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 the tool is for looking up Dogecoin address information, but it provides no explicit guidance on when to use it versus alternatives. It does not mention that it is specifically for Dogecoin addresses (not Bitcoin/Ethereum/etc.), nor does it state any prerequisites like address format validation. With over 200 sibling tools, the lack of explicit routing guidance is a notable gap.

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