hyre-token-snipers

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

No annotations are provided, so the description must bear the full burden. It discloses the behavior (detecting wallets that bought early) and mentions a cost ($0.004), but does not state output format, access restrictions, or side effects. This is a read-only analysis tool, but that isn't explicitly stated.

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 11 words. Front-loaded with the action. The cost is in parentheses, which is minor extra info but doesn't detract. No wasteful 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?

For a single-parameter tool with no output schema, the description gives the core purpose and even a cost. However, it lacks any detail on what the output looks like or any prerequisites (e.g., token must exist). This is acceptable but could be slightly more 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?

Schema covers the single 'mint' parameter with description 'Token mint address' (100% coverage). The tool description adds no parameter-specific semantics beyond what the schema provides; the verb 'Detect' implies the mint is the target, but no additional detail.

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?

Description uses specific verb 'detect' and identifies resource 'wallets' with clear modifier 'that bought in the first few blocks' (sniper analysis). This distinguishes it from sibling tools like hyre-new-tokens or hyre-wallet-pnl.

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 versus alternatives, but the phrase 'sniper analysis' implies a specific use case for analyzing early-buying wallets for a given token mint. Lacks explicit exclusions or comparisons.

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