Hedera: hederaFindTokens

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds search-specific behavior (substring, case-insensitive) but does not contradict annotations. It is accurate but not highly informative beyond what annotations provide.

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 two sentences with no unnecessary words. All information is front-loaded and relevant. Highly concise.

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 covers the return fields and matching logic. It does not mention pagination or rate limits, but for a simple search tool it is reasonably complete.

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 description adds value beyond the schema by specifying that the query is applied to name and symbol, and by listing the return fields (EVM address, name, symbol, decimals). Schema coverage is 100%, so baseline is 3; the extra return field info raises 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 the tool searches Hedera-listed tokens by name or symbol with case-insensitive substring matching, and also lists return fields. This distinguishes it from sibling tools like hederaFindMemeCoins, which targets meme coins.

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 a usage note: omit query to list all tokens, but does not explicitly differentiate when to use this tool over alternatives like hederaFindMemeCoins. The context is clear enough for basic use.

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