get_performance

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

Without annotations, description implies read-only behavior by stating 'Retrieve metrics'. Provides output shape (profit and trade count). Could explicitly state non-destructive nature, but sufficient for a simple fetch tool.

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?

Single sentence, no redundancy, efficiently conveys core purpose and parameter behavior. Front-loaded with key action.

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 simple read tool with one optional parameter, description covers purpose, parameter usage, and output content (profit and trade count). No missing information given complexity.

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 coverage is 100% with detailed description for the single parameter. Description adds minimal extra beyond schema (context of 'per-pair'). Baseline 3 applies.

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?

Description clearly states verb 'Retrieve' and resource 'per-pair trading performance metrics', including specifics 'profit and trade count'. This distinguishes it from sibling tools like get_profit_stats (aggregate) and get_trade (single trade).

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?

Gives guidance on parameter usage ('Optional trading pair... Omit to get all pairs') but does not explicitly compare to alternatives like get_profit_stats or get_balance. No when-not-to-use or exclusion criteria.

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