wafeq_payslips_list

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description includes '🟢 READ-ONLY'. This aligns with annotations. The description does not add details about pagination defaults, filtering behavior, or result ordering beyond what the schema parameters imply.

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-loads the read-only status and endpoint. However, it is slightly redundant: 'List payslips' is repeated verbally and in the title/annotation, and 'Endpoint for retrieving a list of payslips' restates the same idea.

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 simple list endpoint with 11 optional filter parameters and full schema coverage, the description provides the basic purpose and safety profile. It does not mention pagination behavior, default page size, or whether filters can be combined, which would help an agent use it correctly. No output schema exists, so the returned shape is not documented.

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 each parameter already has a description. The tool description itself does not explain how the filter parameters interact (e.g., whether branch, project, and employee are combinable or exclusive), which could add value but is not required given full schema coverage.

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 states a clear verb and resource ('List payslips', 'Endpoint for retrieving a list of payslips') and includes the GET path. It does not explicitly differentiate from sibling tools like wafeq_payslips_retrieve or wafeq_payslips_pay_items_list, but the verb 'list' distinguishes it as the collection endpoint.

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 about when to use this tool versus alternatives such as wafeq_payslips_retrieve or wafeq_payslips_pay_items_list. The description only states what it does, not when it should be chosen.

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