madeonsol_wallet_tracker_watchlist

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds specific behavioral context: it returns labels and capacity limits (BASIC=10, PRO=50, ULTRA=100), which is beyond the annotations and helps the agent understand output scope.

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, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose and a key detail (plan capacities).

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 zero parameters and no output schema, the description is complete: it tells the agent what the tool does, what it returns (wallets with labels and capacity), and the capacity limits per plan. No further information is needed for this simple list operation.

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 zero parameters, and schema coverage is 100%. The description adds meaning by specifying that the output includes labels and remaining watchlist capacity, which is not detailed elsewhere.

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 'List your tracked wallets with labels and remaining watchlist capacity.' This is a specific verb and resource, and it distinguishes the tool from siblings like wallet_tracker_add and wallet_tracker_remove by focusing on listing existing watchlist entries.

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 for viewing tracked wallets but does not explicitly state when to use this tool versus alternatives like wallet_tracker_summary or other list tools. It provides no guidance on prerequisites or exclusions.

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