provider_query_service_accounts

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds nothing beyond the raw HTTP path, and 'all service accounts' is mildly misleading given that page and pageSize are required — the call returns one page, not the full set.

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?

Short but redundant: the title, first line and second line all restate the same fact, and the raw HTTP path adds little value to an agent that already has the name. No front-loaded constraint about paging or filtering.

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 paginated list endpoint with two required parameters, the description omits the pagination requirement, default page size, and the availability of FIQL filtering — the exact things an agent would otherwise get wrong. With no output schema and no annotations covering paging, this is a real gap.

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%, including FIQL filter syntax and sort fields, so the schema carries the parameter burden. The description contributes no additional semantics (no rate limits, no default paging behavior) beyond the endpoint string.

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 ('Retrieve service accounts', 'Get a list of all service accounts') and the underlying endpoint, which distinguishes it from the singular sibling provider_get_service_account. It does not, however, name any sibling or clarify where it sits among provider_query_users / provider_query_groups.

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 provider_get_service_account (single lookup) or the other provider_query_* list endpoints. Nothing tells the agent that pagination parameters are mandatory or that filtering is possible, so selection is left entirely to inference from the name.

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