wafeq_bills_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 description's 'READ-ONLY' and 'retrieving' add no new behavioral information. It does not disclose pagination behavior, response shape, filtering semantics, or any side effects.

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 very short but repetitive: 'List bills' and 'Endpoint for retrieving a list of bills' say essentially the same thing. The front-loaded endpoint/read-only marker is useful, but the redundancy slightly reduces clarity.

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 14 optional parameters, no output schema, and no mention of default pagination, filter behavior, or how parameters combine, the description is too thin to fully guide an agent. The schema covers parameter names, but the endpoint semantics remain under-explained.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The tool description itself adds no parameter-level meaning beyond the schema, but it does not need to because the schema is thorough.

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 tool lists bills and is an endpoint for retrieving a list of bills. It is a specific verb+resource combination that distinguishes it from retrieve/create/update/delete bill tools, though it does not explicitly name any sibling alternative.

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 over wafeq_bills_retrieve, wafeq_bills_create, or other list endpoints. The description merely states what it does, not the conditions or context in which it should be used.

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