books_bulk_print_credit_notes

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'print' without explaining what that entails—whether it generates a PDF, sends to a printer, or has side effects. No mention of required setup or impact.

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—a single phrase. While there is no waste, it is under-specified and does not provide enough substance to be useful. It is brief but lacks necessary structure and content.

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 bulk operation with three parameters, no output schema, and no annotations, the description is completely inadequate. It gives no information about required inputs, behavior, or expected results, leaving the agent without guidance.

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 lists three parameters (orientation, template_id, creditnote_ids) but the description provides zero semantic context. With 0% schema description coverage, the description fails to explain the meaning or usage of any parameter.

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 (print), the resource (credit notes), and the scope (bulk). It distinguishes from sibling tools like books_bulk_export_credit_notes or books_email_credit_notes by specifying 'print' as the 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 export or email credit notes. The description mentions no prerequisites (e.g., template setup) or context for selecting this tool.

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