wafeq_credit_notes_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds minimal extra context: the HTTP method/path (GET /credit-notes/) and the redundant '🟢 READ-ONLY' label. It does not disclose pagination behavior, filtering semantics, or response shape, but with strong annotations the bar is lower and the endpoint detail earns a 3.

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 short and front-loaded with the READ-ONLY badge and endpoint, but 'List credit notes' and 'Endpoint for retrieving a list of credit notes' are redundant restatements of the same idea. A single crisp sentence would have been equally clear.

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 12-parameter list tool with comprehensive schema coverage and safety annotations, the description is adequate but thin. There's no output schema, so a note on return shape or pagination defaults would help, and nothing clarifies that all filters are optional. The openWorldHint also suggests unlisted capabilities that the description doesn't acknowledge.

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?

Schema description coverage is 100%, so every one of the 12 parameters is already documented in the input schema. The description adds zero parameter-level meaning, so the baseline of 3 applies.

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+resource pair ('List credit notes') and confirms it with the collection endpoint 'GET /credit-notes/'. The plural resource and 'list' verb clearly distinguish it from siblings like wafeq_credit_notes_retrieve, though it doesn't explicitly name them.

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 on when to choose this tool over alternatives. The description merely states what the endpoint does ('Endpoint for retrieving a list of credit notes') without explaining scenarios, exclusions, or how it differs from retrieve/create/destroy siblings. Nothing is left to inference except the generic meaning of 'list'.

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