get_top_trading_strategies

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: it returns two separate ranked lists, explains what fields each entry contains, documents the five sort options with their meanings, and specifies default values. However, it doesn't mention rate limits, authentication requirements, or error conditions.

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 well-structured and appropriately sized, starting with the core purpose, then detailing return format, then sort options, then parameters. While comprehensive, some sentences could be more concise, and the field listing is quite detailed but necessary for understanding the output.

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?

Given the tool's complexity (multiple sort options, detailed return structure) and the presence of an output schema, the description is remarkably complete. It explains the dual-list return format, documents all sort options with semantics, fully describes parameters, and references the output structure. The output schema existence means the description doesn't need to exhaustively document return values.

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?

Despite 0% schema description coverage, the description fully compensates by providing comprehensive parameter semantics. It explains both parameters in detail: 'sort' with all five possible values and their meanings, and 'limit' with its range (1-20) and default. This adds significant value beyond the bare schema.

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 the tool's purpose: to retrieve top-ranked trading strategies, specifically distinguishing between short volatility and long volatility strategies. It explicitly names the resource (trading strategies) and verb (get), and differentiates itself from sibling tools like get_ticker by focusing on ranked lists rather than individual ticker data.

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 context by specifying it returns ranked lists of strategies, but doesn't explicitly state when to use this tool versus alternatives like get_ticker or search tools. No guidance is provided about prerequisites, timing, or when-not-to-use scenarios.

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