Profit Analysis (Realized, US)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds useful behavioral info: region restriction and error behavior ('DcRegionRestricted'). No contradiction with 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 sentences (25 words). Front-loaded with main action and scope. No superfluous information. Every sentence adds value.

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?

Combined with comprehensive annotations and existing output schema, the description fully specifies behavior: what it does, constraints, and error conditions. Complete for an agent to use correctly.

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?

Input schema provides clear descriptions for both parameters (category and currency) with 100% coverage. Description reinforces that currency is typically USD and the tool is US-only. Adds value by clarifying region restriction, which impacts parameter usage.

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 explicitly states 'Get realized P&L for a US account, broken down by category and period.' Clearly specifies verb (get), resource (realized P&L), and scope (US accounts). Distinct from sibling profit_analysis and profit_analysis_detail by focusing on realized and US-only.

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?

Explicitly states 'US accounts only; errors with DcRegionRestricted for HK/CN/SG accounts.' Provides clear context for when to use (US accounts) and when not to (other regions). Does not mention alternative tools for non-US accounts, but the error message effectively guides agents away from misuse.

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