Capital Titans

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is handled. The description adds behavioral context beyond annotations by specifying the return fields and explaining that minPnl/minFees gates 'filter out noise,' which gives the agent a sense of how results are scoped. There is 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 compact and front-loaded: the core ranking concept is in the first sentence, outputs in the second, and usage guidance in the third. Every sentence earns its place without filler or repetition of schema details.

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 read-only filtered ranking tool with no required parameters and no output schema, the description sufficiently covers what the tool does, what it returns, and when to use it. The return-field list compensates for the missing output schema, and the schema covers all parameter defaults and constraints.

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 description coverage is 100%, so the baseline is 3. The description adds value by explicitly contextualizing minPnl and minFees as noise-filtering gates, which reinforces their semantic purpose beyond the schema's one-line descriptions. It does not need to restate the other parameters.

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: 'Find the most fee-efficient traders' and defines the ranking metric as 'highest realized PnL per dollar of fees paid.' It also lists the exact returned fields, which makes the tool's identity and output unambiguous. Although the title 'Capital Titans' is vague, the description clearly distinguishes this tool from the many sibling trader-ranking tools by focusing on PnL-per-fee-dollar efficiency.

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 gives an explicit use-case quote: 'who extracts the most edge per dollar spent on fees?' This tells an agent when to reach for this tool. It does not name alternatives or exclude scenarios, but the stated use case is clear enough for selection.

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