wafeq_simplified_invoices_list

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description adds essentially no behavioral context beyond repeating 'READ-ONLY' and 'GET'. It does not disclose pagination behavior, filtering semantics, or any other runtime traits beyond what annotations and schema already provide.

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 a useful READ-ONLY badge and endpoint path, but it contains redundancy: 'List simplified invoices' and 'Endpoint for retrieving a list of simplified invoices.' say the same thing, so the last sentence does not earn its place.

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 11 optional filter parameters, no output schema, and close siblings such as wafeq_simplified_invoices_retrieve and wafeq_invoices_list, the description is too thin. It does not mention that the endpoint supports filtering by branch, contact, project, dates, or timestamps, nor does it distinguish listing from retrieval.

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 all 11 parameters already have individual descriptions. The tool description adds no extra parameter meaning, which matches the baseline of 3 when the schema carries the documentation burden.

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 names the exact operation ('List simplified invoices') and resource, and the endpoint path 'GET /simplified-invoices/' reinforces the scope. The 'Simplified Invoices' qualifier clearly separates it from the sibling wafeq_invoices_list, so an agent can tell what resource is being acted on.

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?

The description implies this is the tool to use when a list of simplified invoices is needed, but it gives no explicit when-to-use/when-not-to-use guidance. It does not mention alternatives such as wafeq_simplified_invoices_retrieve for a single invoice or wafeq_invoices_list for regular invoices, leaving the agent to infer from the name.

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