books_get_credit_notes

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

With no annotations, the description carries the full burden of behavioral disclosure. It claims to 'Get all credit notes' but does not mention that the results are paginated (via page and per_page parameters), nor any sorting/filtering behavior. This is a significant omission for a list endpoint.

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 a single short sentence, technically concise. However, it is under-specified for a tool with 13 parameters, offering no structural detail about the response or the filtering capabilities. This is not concise completeness but rather lack of specification.

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 (13 parameters, no output schema, no annotations), the description is drastically incomplete. It does not explain what fields are returned, how pagination works, or the meaning of key filters, making it nearly impossible for an agent to use 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 schema contains 13 parameters with zero description coverage. The tool description adds no parameter-level meaning whatsoever, failing to compensate for the schema's lack of documentation. This is a major gap for parameters like filter_by, sort_column, and search_text.

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 a specific verb ('Get') and resource ('all credit notes from Books'), clearly indicating this is a list operation. It distinguishes from the singular sibling 'books_get_credit_note' by saying 'all credit notes'.

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 the many other get_* tools. The description does not mention any exclusions, prerequisites, or scenarios where an alternative would be more appropriate.

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