madeonsol_wallet_tracker_trades

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

The description adds valuable behavioral info beyond annotations: data is truncated and no tx_signature is included. Annotations already indicate read-only, open-world, idempotent, non-destructive, so no contradiction. The truncation disclosure is helpful.

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 extremely concise with two sentences that capture the core purpose and a key limitation. No unnecessary words or repetition.

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 simple read-only tool with good schema and annotations, the description is adequate but lacks details on what 'truncated wallets' means, pagination behavior beyond the before parameter, and expected output structure (no output schema). Could be slightly more comprehensive.

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 input schema has 100% coverage with parameter descriptions, so the description does not need to add much. The tool description only adds a general limitation (truncated data), not per-parameter detail. Baseline 3 is appropriate.

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 returns historical swap and transfer events for watched wallets, and it adds a specific limitation note (BASIC: truncated wallets, no tx_signature), distinguishing it from similar tools like madeonsol_wallet_trades.

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 usage context (for watched wallets) but does not explicitly state when to use this tool versus alternatives like madeonsol_wallet_trades or other wallet tools. No when-not or exclusion criteria are provided.

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