madeonsol_kol_feed

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds context about real-time data from an in-memory price tracker with millisecond accuracy and mentions PRO+ filters, but does not disclose rate limits or any limitations. It adds some value beyond annotations but is not comprehensive.

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 concise (two sentences), front-loaded with the core purpose in the first sentence, and uses the second sentence to add context about speed and PRO+ features. Every sentence earns its place without wasted 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?

With 9 parameters and no output schema, the description provides the key output detail (market cap at trade time) but omits the full structure of returned trades. While annotations are good, more detail on the response format would improve completeness for an agent.

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%, with all 9 parameters described in the input schema. The description mentions PRO+ filters for some parameters but adds no additional meaning to the schema descriptions. Baseline score of 3 is appropriate since the schema already does the heavy lifting.

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 it retrieves real-time KOL trades from over 1,000 tracked wallets, with market cap data. This distinguishes it from sibling tools like madeonsol_kol_hot_tokens or madeonsol_kol_leaderboard, which serve different purposes.

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 real-time trade monitoring and mentions speed advantages, but does not explicitly state when to use this tool versus alternatives like madeonsol_kol_alerts_recent or madeonsol_kol_hot_tokens. No when-not-to-use guidance is provided.

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