get_bill_history

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Retrieve' and 'past billing history' communicate that this is a read-only historical lookup, which is useful, but the description does not discuss authentication expectations, response shape, or any limitations. It adds some behavioral context but not comprehensive coverage.

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 a single sentence that front-loads the main action and resource, then adds the most relevant output details. There is no wasted wording or redundant information.

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?

The tool has no output schema and no annotations, so the description must cover behavior and result content. It names the key returned data fields and the read-only nature, but it does not mention usage context, alternative tools, or limitations such as how far back history goes beyond the schema's months parameter. It is adequate but has clear gaps.

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 description coverage is 100%, so the parameters are already fully documented in the schema. The description does not add parameter-specific meaning, but it does help by indicating the returned data fields, which indirectly clarifies the value of the history request. This meets the baseline for full schema coverage.

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 uses a specific verb 'Retrieve' and a clear resource, 'past billing history for a Spectrum account', and adds concrete content details: bill dates, amounts, and payment status. This distinguishes it from siblings like get_account_overview and pay_bill without needing further explanation.

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 implies usage for retrieving billing history, which is distinct from paying a bill or checking outages, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. No direct routing guidance is provided.

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