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

With no annotations, the description carries the full burden. It does add real semantic context — that the ranking reflects copies held vs distinct owners, with a concrete example (33 copies in one collection vs one copy across 400 people) — but it says nothing about data freshness, scope of 'tracked' portfolios, or result shape.

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?

Front-loaded with the resource and its scope, then the differentiating signal, then the ranking semantics. Three sentences with no filler, though the closing example is illustrative flourish that is useful but not strictly required.

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 6-parameter list tool with no annotations and no output schema, the description covers the metric well but omits how results are returned (fields, whether owner counts are included), pagination behavior, and the relationship to the sibling holdings tool. Adequate but with clear gaps.

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 67%, so the enum parameters (kind, sort, direction) are already documented in the schema. The description re-explains the sort distinction in prose, which reinforces but does not extend the schema; query filtering and pagination are left entirely to the schema.

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 states clearly that this returns the Limiteds and creators most held across tracked portfolios, and it frames the returned signal (aggregate holding behavior, not price or sales). It distinguishes itself from price/volume tools conceptually, though it never names the near-sibling get_player_holdings, so the boundary is inferable rather than explicit.

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?

'A different signal from price or sales volume' gives implicit guidance on when to pick this over market-cap/sales tools, and the sort explanation clarifies the two ranking modes. However, there is no explicit when-to-use/when-not, no mention of get_player_holdings as the alternative for individual collector data, and no prerequisites.

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