books_refund_credit_note

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

The description only states 'Create a refund for a credit note' with no details about side effects, such as whether the credit note's remaining balance is reduced, whether refunds are reversible, or any permission requirements. Since annotations are absent, the description carries the full burden but fails to disclose these behaviors.

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 very concise with a single sentence, which is good for front-loading, but it is under-specified for an 8-parameter financial operation. It could include additional context without becoming verbose.

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's complexity (8 parameters, no annotations, no output schema), the description is overwhelmingly incomplete. It provides no context about return values, side effects, or parameter semantics, making it insufficient for reliable invocation.

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 description does not mention any of the 8 parameters, and schema description coverage is 0%. It fails to explain key fields like refund_mode, exchange_rate, or from_account_id, leaving the agent without essential semantic context.

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 ('Create a refund') and the resource ('a credit note'), which is specific. However, it does not explicitly differentiate from sibling tools like books_get_credit_note_refunds, though the verb 'create' implies a write operation.

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 such as books_create_credit_note or books_get_credit_note_refunds. There is no mention of prerequisites, like whether the credit note must be in a certain state, or scenarios where this tool is appropriate.

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