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

No annotations are provided, so the description carries the full burden. It discloses critical behavioral traits: verdict-free output, explicit errors for partial sub-analyses rather than silence, and 'not financial advice'. It also notes the required query parameter. It does not explicitly state read-only or side-effect-free, but for a data-analysis sweep this is reasonably implied; the disclosed traits are valuable and non-obvious.

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 dense paragraph, front-loaded with the main purpose, and each clause adds information (components, verdict-free, error handling, not advice, requirement). It is somewhat long but justified given the tool's complexity; no wasted words. A 4 reflects good structure without being overly terse.

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 tool with no output schema and no annotations, the description explains what the tool returns (checklist, verdict-free), how it handles partial results (explicit errors), and the required parameter. It does not mention pagination or potential limits, but these are not critical for a sweep tool. Overall it covers the key usage aspects well, meriting a 4.

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 100% for the single 'mint' parameter, which already includes an example. The description adds little beyond the schema, merely restating that the sweep requires a mint address. With full schema coverage, the baseline of 3 is appropriate; the description doesn't provide extra semantic detail beyond what the schema offers.

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 opens with a specific verb-resource pair ('PRE-TRADE SWEEP for a token') and enumerates exactly what the bundle contains: token-intel (risk + digest + holder classification), a wallet-activity profile of the largest holder, and priority-fee bands. This clearly distinguishes it from the sibling tools like solmachina_token_risk or solmachina_token_holders, which individually cover only parts of this sweep.

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 a one-call alternative to multiple sibling calls, but does not explicitly state when to prefer this over separate tools or name exclusions. It gives strong contextual cues (pre-trade, one-call) but lacks an explicit when-not or alternative guidance, so it earns a 4 rather than 5.

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