get_strategy_performance

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

With no annotations, the description must cover behavioral aspects. It lists specific returned metrics and notes the authentication requirement. It does not mention potential errors, rate limits, or that it is read-only, but it provides sufficient context for an agent to understand the tool's non-destructive nature.

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 extremely concise with two sentences that front-load the purpose and list outputs, then provide the authentication requirement. No wasted words.

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?

There is no output schema, so the description must explain return values. It lists key metrics but not all possible details (e.g., format of NAV data, error handling). It covers the main points but misses some completeness for a first-time user.

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 schema already explains each parameter. The description adds value by reiterating the need for an API key and hinting at its acquisition via register_trial, but does not add significant new semantics beyond the 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 it gets performance metrics for a specific strategy, listing returns, drawdown, Sharpe, win rate, and daily NAV history. This distinguishes it from siblings like compare_strategies (compares multiple) and list_strategies (lists all).

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 mentions requiring an API key from register_trial, indicating a prerequisite. However, it does not explicitly guide when to use this tool versus alternatives like compare_strategies or get_signals, leaving some ambiguity.

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