check_charge_reason_code

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

No annotations exist, so the description carries the full burden. 'Check whether' signals a read-only validation predicate, and 'recognized' indicates membership against a canonical codelist, but behavior on unknown values, case sensitivity, and error conditions are not disclosed. This is adequate for a simple check tool, but not much more.

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 short sentence with no filler; every word contributes meaning. However, the extreme brevity also leaves behavioral details underspecified, so it earns high but not top marks for structure.

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 one-parameter read-only check with an output schema, the core action is clear. The main gap is that the description does not indicate where valid charge reason codes come from or mention list_charge_reason_codes as the way to discover them, leaving some ambiguity around 'recognized.'

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 0%, so the description must compensate. It identifies *code* as the value being checked, but gives no format, length, case, or accepted source; this role is nearly identical to the property name and tool name, so the added meaning is minimal.

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 opens with a specific action ('Check whether') and a specific resource ('recognized charge reason code'), making the tool's predicate behavior unmistakable. It also differentiates from the sibling list_charge_reason_codes by implying membership testing rather than enumeration.

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?

There is no when-to-use guidance, no mention of alternatives, and no exclusion criteria. With many list/check sibling tools, the agent is left to infer that this tool validates a single code and that list_charge_reason_codes would be used to enumerate valid values.

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