books_get_credit_note_refunds

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

There are no annotations, and the description provides zero behavioral details. It does not disclose return type, pagination, read-only nature, or any other contextual behavior, making it completely opaque beyond the basic operation.

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 short, but it is under-specified rather than concise. The brevity does not serve a purpose because it omits essential context that would be useful to an agent.

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 has pagination parameters and a required creditnote_id, the description is grossly incomplete. It does not mention that the tool likely returns a list, how pagination works, or any details about refund records, and there is no output schema to supplement.

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 description coverage is 0%, and the description does not explain any of the three parameters. It fails to compensate for the missing schema descriptions, leaving parameter semantics entirely undocumented.

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 'Get' and the resource 'refunds for a credit note', making it clear what the tool does. However, it does not distinguish this from sibling tools like books_get_credit_note or books_refund_credit_note, so it lacks the differentiation for a 5.

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 usage guidance is provided. The description does not mention when to use this tool over alternatives, prerequisites, or exclusions. It only implies its function via the verb 'Get', which is not sufficient guidance.

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