Profit Analysis Detail

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, so no side effects are expected. The description adds transparency about the date range behavior (empty results if unpaired), which is useful beyond the 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 only two sentences: first sentence covers purpose, second covers parameter usage. It is front-loaded with the main action and resource, and every word earns its place.

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 simplicity (3 parameters, 1 required, no output schema), the description provides all necessary context: purpose, parameter constraints, and result behavior. The annotations cover safety and idempotency, making it complete.

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 already has descriptions for all parameters, so baseline is 3. The description adds value by explicitly stating the consequence of passing only one date parameter (returns empty results), which is not in 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 the action ('Get') and the resource ('detailed profit and loss analysis for a specific symbol'), making the purpose immediately obvious. It distinguishes from sibling tools like profit_analysis by specifying 'detailed' and requiring a symbol.

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 provides explicit guidance on the date range parameters: both start and end must be provided together, otherwise empty results. This helps avoid misuse. However, it does not mention when to choose this tool over alternatives like profit_analysis or when not to use it.

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