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

With annotations empty, the description carries the full burden, and it does add valuable non-obvious context about access: x402 payment of 0.02 USDC or API key auth. However, it does not disclose the return shape, whether holdings are a live snapshot vs cached, or pagination behavior, leaving behavioral gaps.

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-loads the resource and scope, follows with a concrete use case, and brackets the access/payment note so it doesn't obscure the main purpose. Efficient with no filler.

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 four-optional-param read tool with no output schema and no annotations, the description covers purpose, selection condition, and payment/auth requirements. It could say more about what a holding record contains, but it is adequately complete for correct invocation.

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%, so all four parameters are already documented. The description only adds that results are 'sorted by USD value' and hints at the Fund/Smart Trader label scope, which the include_labels schema also covers. Baseline 3 is appropriate since the schema 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?

States a specific resource and scope: 'Current smart-money holdings: what funds and smart traders are holding right now, sorted by USD value.' This clearly distinguishes it from trade/flow siblings like get_smart_money_flows, though it only implicitly differentiates from the very close get_smart_money_historical_holdings via the word 'current' rather than naming it.

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?

Explicit when-to-use guidance: 'Use it when the user asks what smart money currently owns or has positions in.' There are no exclusions or named alternatives (e.g., historical holdings for past positions), so it stops short of full routing guidance.

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