Fetch all sip users

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description's 'Read-only' merely restates that. The endpoint path (GET /sip_users) is minor added context, but pagination behavior, whether filters combine, and default result size are left undisclosed.

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?

Three short fragments with zero waste; the resource is front-loaded and the endpoint/read-only metadata follows.

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?

A list endpoint with seven optional parameters and no output schema needs at least a note on pagination and filtering behavior; the description provides none. Annotations carry the safety profile and the schema carries parameter meaning, so the remaining gap is moderate rather than critical.

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 all seven parameters (page, per_page, four filters, response_format) are already documented in the schema. The description adds nothing about filter semantics or the caveat that per_page is not honored by every endpoint, so the baseline 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?

States a specific verb and resource ('Fetch all sip users') and the plural 'all' implicitly distinguishes it from the sibling placetel_get_sip_user. It stops short of explicitly naming that sibling or the related create/update/delete SIP user tools it should not be confused with.

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 use this versus placetel_get_sip_user (single record) or when a filtered list is preferable. 'Read-only' is the only contextual signal, and it is already conveyed by annotations.

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