create_adhoc

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

No annotations are provided, so the description carries full burden. It states the tool performs a charge operation but provides no behavioral details about permissions required, whether this is reversible, rate limits, error conditions, or what happens after charging. For a financial transaction tool with zero annotation coverage, this is insufficient.

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 extremely concise (5 words) with zero wasted words, though it may be too brief given the tool's complexity. It's front-loaded with the core action but lacks necessary elaboration for a financial transaction tool.

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 financial charging tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'ad-hoc' means, what the tool returns, error handling, or how it differs from sibling payment tools. The minimal description fails to compensate for the lack of structured metadata.

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 schema already documents all three parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, maintaining the baseline score of 3 where schema does the heavy lifting.

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 states the action ('Charge') and resource ('tokenized card'), but is vague about scope and lacks sibling differentiation. It doesn't specify what 'ad-hoc' means operationally or how this differs from similar tools like 'create_payment' or 'refund_payment'.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'create_payment' and 'refund_payment' available, the description offers no context about appropriate use cases, prerequisites, or exclusions for this specific charging method.

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