sherweb_billing_charge_details

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

With no annotations provided, the description carries the behavioral burden. It usefully discloses that Sherweb exposes charges only as a billing-period collection, so the tool must read the period and select the matching charge. This non-obvious workaround is exactly the kind of behavioral context agents need. It does not discuss rate limits or auth, but 'Get full detail' makes the read-only nature reasonably clear.

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 with no filler. The primary purpose is front-loaded, and the second sentence explains a crucial behavioral constraint without unnecessary detail.

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?

Although there is no output schema or annotation context, this is a simple two-parameter lookup. The description explains the key billing-period behavior and the schema handles parameter guidance. It is complete enough for an agent to call the tool correctly, though a brief note on what fields 'full detail' contains would make it even stronger.

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 baseline is 3; the schema already documents both parameters well, including the 'Use this when the charge falls outside the current period' guidance for the date parameter. The description adds context by explaining why the period is needed, but it does not add substantial new per-parameter meaning beyond 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 the full detail of one charge') and the resource ('charge by its ID'). It distinguishes itself from the sibling list tool 'sherweb_billing_payable_charges' by focusing on a single charge's full detail rather than a collection, though it does not explicitly name or contrast that sibling.

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 when to use the tool: when you need one specific charge's details by ID. The date parameter schema adds useful guidance for charges outside the current period, but the description itself does not explicitly state alternatives, exclusions, or when to prefer a sibling tool like the payable charges list.

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