tebra_get_charges

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

No annotations provided; the description indicates it returns charge details but lacks disclosure of default behaviors, pagination, limits, or side effects. It conveys read-only intent but fails to cover these details.

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 concise sentences. The first sentence establishes purpose and key filters; the second states the output. No wasted words.

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?

With 18 optional parameters and no output schema, the description is brief and omits pagination, default sort order, and result limits. Adequate but leaves unanswered questions for complex queries.

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%, and the description merely echoes common filter categories already in the schema. It adds minimal value 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 retrieves charges with flexible filters and specifies the return fields. It effectively distinguishes from sibling tools like payments and transactions by focusing on charge-specific filters.

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 use for retrieving charges but does not explicitly advise when to use this over alternatives (e.g., tebra_get_payments) or when not to use it.

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