books_create_credit_note

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

No annotations are present, so the description must fully disclose behavioral traits. It only says 'Create a new credit note' without explaining whether the credit note is created as draft or final, how taxes or discounts are applied, or what the response contains. This is a significant gap for a mutation tool.

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 single sentence is concise but under-specified. While it efficiently states the purpose, it omits essential operational details, making it too brief for a complex tool with many parameters and sibling operations. It is not a balanced tradeoff between brevity and completeness.

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 (23 parameters, nested objects, 1 enum) and many related sibling tools, the description is grossly incomplete. It does not mention the relationship to invoices, how line items work, or any business rules, leaving the agent without enough context to use the tool correctly.

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 provides zero parameter semantics. With 23 parameters and 0% schema description coverage, the agent is left with only parameter names and types, which is insufficient for correct invocation. The description does not compensate for the lack of 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 uses the specific verb 'Create' with the resource 'credit note in Books', clearly identifying the tool's operation. This distinguishes it from sibling tools like update, delete, void, or convert credit note operations.

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_apply_credit_note_to_invoice or books_convert_credit_note_to_open. There is no context about prerequisites, linking to invoices, or when a credit note should be created.

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