create_customer_charge_credit

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

No annotations are provided, so the description bears full responsibility. It mentions the API endpoint (POST) and important notes about amount units and conditional weight requirement. However, it does not disclose other behavioral traits such as side effects, idempotency, authorization needs, or error handling.

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 concise and well-structured, front-loading the purpose and endpoint, then providing a clear list of required/optional parameters. It avoids unnecessary verbosity but could be slightly more streamlined.

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 the tool has 10 parameters, no output schema, and no annotations, the description covers the essentials but lacks information about return values, error scenarios, and idempotency. It is adequate for a creation tool but not fully complete.

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 covers 100% of parameters, so baseline is 3. The description adds value by emphasizing that amount is in cents with examples, clarifying that weight is required when category is physical, and listing required vs. optional parameters in a readable way.

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's purpose: 'Create a charge or credit for a customer.' It uses a specific verb and resource, distinguishing it from siblings like delete_customer_charge_credit and list_customer_charges_credits.

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 specifies required and optional parameters but does not explicitly state when to use this tool over alternatives. However, it is clear that this is for creating a charge/credit directly, unlike other tools for charging invoices. No exclusion criteria are given, but the context is adequate.

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