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

No annotations are present, so the description carries the full burden. It discloses pricing, data source (on-chain tracker), and that it is educational data, not financial advice. It does not explicitly state read-only behavior or potential side effects, but the 'get' verb and raw data context make it inferable.

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 long but each sentence adds value: data scope, source, pricing, payment methods, and a pointer to get_catalog. It is front-loaded with the core purpose and then details, though it could trim the payment explanation. Still, it is dense and structured.

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?

The description covers what data is returned (address, volumes, counts, markets, cabal cluster ideas), the payment/auth mechanism, and the optional limit. With a single parameter and no output schema, this is sufficient for an agent to invoke and interpret results. It lacks explicit error handling notes but that is not critical.

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?

With 0% schema description coverage, the description compensates by explaining the limit parameter: optional, default 25, cap 100. This adds critical meaning beyond the schema (which only shows default), making the tool callable correctly.

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 Polymarket flagged-wallet groupings and coordinated-betting cabal intel, which is specific and distinguishes it from similar sibling tools like get_polymarket_new_wallets or get_polymarket_whale_leaders. It doesn't explicitly name alternatives, but the purpose is unambiguous.

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 provides payment and invocation details, but it does not explain when to use this tool versus the many sibling tools (e.g., when to prefer whale leaders vs groupings). There is no context on use cases or exclusions, leaving agents to infer applicability from the data description.

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