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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds critical context: this is a paid tool costing $0.85-$1.00 per call from Einstein credit, and which modes produce what kind of output (leaderboard list vs intel analysis). This goes beyond annotations meaningfully.

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 two sentences with no wasted words. The primary purpose is front-loaded, and the pricing/alternative note is neatly bracketed. It efficiently communicates both modes and cost.

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 both operational modes, pricing, and free-alternative guidance. With no output schema, it gives a sufficient high-level sense of what is returned (ranked list, intel on edge/consistency/risk), though it does not detail exact fields or ranking criteria.

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 the baseline is 3. The description enriches the meaning of the `kind` parameter by specifying that leaderboard returns 'profitable wallets worth following' and intel provides a 'deeper intelligence read' on edge, consistency and risk—details not present in the schema's enum description.

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 two distinct functions: a 'ranked leaderboard of profitable wallets worth following' and a 'deeper intelligence read on a specific trader’s edge, consistency and risk'. It uses specific resource terms and distinguishes the tool's scope (copy trading) from siblings.

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 scenarios via the two modes (leaderboard vs intel) and mentions 'Free alternatives exist... see list_einstein_capabilities', but it does not explicitly state when to prefer this tool over alternatives or provide exclusions. Context is present but not fully directive.

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