getCopyTradingClassicLeaderboard

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

The annotations already indicate readOnlyHint and openWorldHint. The description adds meaningful behavioral context: the list is curated, the returned order is the intended presentation order, and candidates expose 30-day return, max drawdown, and Sharpe ratio metrics. No contradiction with annotations.

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 front-loaded with a clear purpose statement and then moves into return semantics and agent workflow. It is long, but each section serves a practical purpose; the example success message is somewhat optional but still useful for a conversational flow.

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 no-argument read-only tool, the description covers what is returned, how the returned order should be used, what metrics matter for comparison, and how to proceed to the bind endpoint. The absence of an output schema is partially offset by this rich description, though an explicit field list would be even clearer.

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?

The tool has zero parameters and the schema coverage is 100%, so there is nothing for the description to add about inputs. The baseline for a parameterless tool is 4, and the description appropriately focuses on output and usage.

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 a precise verb and resource: 'Get a curated Copy Trading Classic leaderboard'. It also names the intended use case, 'conversational recommendation flows', and distinguishes the tool from its sibling getCopyTradingTradFiLeaderboard by explicitly calling for both lists to be presented separately.

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?

It gives an explicit trigger condition: 'If a user asks for a reliable copy trader or similar recommendation, call both...' It also tells the agent how to present, compare, and continue to the bind endpoint, making the decision path unambiguous.

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