getCopyTradingTradFiLeaderboard

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that the endpoint returns a ranked list, that the returned order is presentation order to be preserved, and that key comparison fields include 30-day return, 30-day max drawdown, 30-day Sharpe ratio, and providerMark. No annotation contradiction.

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 first sentence is front-loaded and states the core purpose, and the agent hint is clearly separated. The description is long and includes a full conversational script plus a success-message template, which adds actionable context but goes beyond what is strictly necessary for a no-parameter read endpoint.

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?

With no parameters and no output schema, the description fully compensates by specifying the ranked return, ordering semantics, the comparison metrics, the mapping to providerMark, and the follow-up bind endpoint. Nothing essential is missing for correct invocation and result interpretation.

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 input schema has zero parameters and 100% schema description coverage, so there are no parameter semantics to clarify. The baseline for a no-parameter tool is 4; the description instead usefully explains what the returned data contains.

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 opens with a specific verb and resource: 'Get a curated Copy Trading TradFi leaderboard' and states its purpose ('for conversational recommendation flows'). It distinguishes itself from the sibling getCopyTradingClassicLeaderboard by name and instructs the agent to call both, making the scope 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?

Usage guidance is explicit: 'If a user asks for a reliable copy trader or similar recommendation, call both the Copy Trading Classic leaderboard endpoint and this Copy Trading TradFi leaderboard endpoint.' It even specifies the downstream bind endpoint and user-selection flow, so an agent knows exactly when and how to use this tool versus alternatives.

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