Get Smart Money Feed

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

Annotations already indicate readOnly, destructive, idempotent, and openWorld hints. The description adds context about PulseX and whale movements, but no additional behavioral details (e.g., rate limits, data freshness) beyond what annotations provide.

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 concise sentence with an additional requirement line. It is front-loaded, with no wasted words, and every sentence serves a clear purpose.

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 that an output schema exists (context signals indicate 'has output schema: true'), the description does not need to detail return values. It adequately covers the tool's function and requirements, though it could mention list structure or pagination if needed.

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 description coverage is 100% and the parameters are well-documented in the schema. The description does not add extra meaning beyond what the schema already provides for hours and min_usd.

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 that the tool retrieves smart money/whale activity feed for large wallet movements and swaps on PulseX. It is specific about the resource and action, though it does not explicitly differentiate from the similar sibling 'get-whale-alerts'.

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 mentions it is a '[PRO]' tool and requires an API key, but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. The purpose is implied but not structured as usage advice.

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