Hedera: hederaFindMemeCoins

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, providing a strong safety profile. The description adds the source 'MemeJob' but does not disclose paging or ordering behavior beyond what the schema implies. Given annotations, it is adequate but not enhanced.

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 sentence that directly states the core purpose. It is concise and easy to parse, though it could benefit from a brief note on pagination or usage.

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 lacks details about return values (no output schema), pagination behavior, and ordering options. For a tool with multiple parameters and no output schema, more context is needed for an agent to fully understand its capabilities.

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 50% (only 'page' and 'limit' have descriptions; 'orderBy' and 'orderDirection' lack descriptions). The tool description does not compensate for the missing parameter documentation, leaving those parameters unclarified.

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 action (find) and resource (memecoins) with a specific source (MemeJob on Hedera). However, it does not distinguish from the sibling tool 'hederaFindTokens' which might also find tokens, but memecoins are a subset. The distinction is implicit but not explicit.

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 guidance on when to use this tool vs alternatives such as 'hederaFindTokens', 'getPumpFunTokens', or 'baseFindClankerTokens'. The description lacks context for appropriate usage, leaving the agent without decision support.

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