wafeq_debit_notes_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description only repeats READ-ONLY and the HTTP method. It adds no behavioral context such as pagination behavior, default sorting, or result-set characteristics, so it contributes little beyond the annotations.

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 endpoint, but it is redundant: 'List debit notes' and 'Endpoint for retrieving a list of debit notes' say the same thing. Two of the three sentences add little unique value.

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?

With 12 optional parameters and no output schema, the description should explain filtering, pagination, or return expectations, but it does none of this. It is complete only for the most trivial reading of the tool.

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%, and the description provides no additional parameter semantics. The baseline of 3 applies because the schema already documents all 12 parameters, although several schema descriptions are not particularly informative.

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 and resource: 'List debit notes' and 'GET /debit-notes/'. It is unambiguous about the target resource, though it relies on the resource name rather than explicitly distinguishing this list endpoint from sibling list tools like credit notes, bills, or invoices.

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?

There is no guidance on when to choose this tool over alternatives, no exclusions, and no mention of intended use cases or filtering scenarios. The text only restates that the tool retrieves a list of debit notes, leaving usage selection entirely to the agent.

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