getBillingHistory

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

With no annotations provided, the description carries the full burden. It clearly discloses the sensitive redaction behavior ('Payment cards ... automatically redacted with [REDACTED] by the DLP engine'), and the verb 'Retrieve' implies a read-only operation. It does not discuss authorization or rate limits, but the redaction disclosure is valuable and goes beyond the name/schema.

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 compact and front-loaded. The first sentence immediately states the resource and operation, and the second sentence adds one crucial behavioral detail. No wasted words or repetition of schema fields.

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-only tool with one parameter and no output schema, the description covers the key return contents (statements, balance, payment methods, invoice IDs) and the DLP redaction behavior. It is missing potential error scenarios, but this is not critical for a straightforward retrieval tool.

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 schema provides 100% coverage for the single parameter, including an example and format description. The description adds no new semantics beyond referring to 'a specific customer', which is already implied by schema coverage. Baseline 3 is appropriate.

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 states a specific verb ('Retrieve') and a distinct resource ('customer billing statements and payment methods'), and enumerates concrete data components (balance due, payment methods, invoice IDs). This clearly separates it from sibling tools like getCustomerDetails or listSupportTickets, which serve different purposes.

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?

No guidance is provided on when to use this tool versus the listed sibling tools. The description explains what the tool does but not when an agent should choose it over alternatives, nor does it mention any exclusions or prerequisites.

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