Get P&L Report

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

Without annotations, the description discloses key behaviors: exclusions, parameter interactions, unattributed bucket, and render field. It does not mention permissions, rate limits, or data freshness, but for a read tool the disclosure is substantial.

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 four sentences with no filler. It front-loads the main purpose, then adds critical nuances. Every sentence 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 no output schema, the description explains the key output aspects (category breakdown, optional by-customer rollup, render field). It could detail the return fields more, but the render field guidance compensates. Adequate for the 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%, so baseline is 3. The description adds value by explaining the interplay between customer_id and group_by_customer, and the unattributed bucket, which goes beyond the schema descriptions.

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 returns a profit & loss summary grouped by category for a date range. It uses specific verbs and resources, distinguishing it from generic list tools. Although a sibling 'get_financial_summary' exists, the description uniquely specifies grouping and report scope.

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 when to use customer_id vs group_by_customer and mentions the exclusion of certain transactions. It does not explicitly list when not to use the tool or contrast with siblings like get_financial_summary, but the context for parameter usage is clear.

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