Profit Analysis Detail

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

Annotations already mark the tool as readOnly, openWorld, idempotent, and non-destructive, ensuring an agent knows it's safe. The description adds key behavioral insight: providing only one of the date parameters returns empty results. This goes beyond 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?

Two concise sentences: first states the main action, second clarifies parameter usage. No filler, front-loaded with purpose, efficient.

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 tool with 3 parameters and no output schema, the description covers the purpose, required symbol, and optional date constraints with behavior. It could optionally mention the response nature, but it is adequately complete for its simplicity.

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 covers 100% of parameters, but the description reinforces the mutual dependency of start and end dates and explicitly states the empty result behavior for incomplete pairs. This adds practical value beyond the schema constraints.

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 retrieves 'detailed profit and loss analysis for a specific symbol,' using a specific verb and resource. It distinguishes from the sibling 'profit_analysis' by emphasizing 'detailed,' indicating a more granular report.

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 explains how to use the date parameters (both required together) and the consequence of misuse (empty results). However, it does not provide guidance on when to use this tool versus its sibling 'profit_analysis' or any other alternative.

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