acronis_fetch_users_batch

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

Annotations already declare readOnlyHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: no mention of the 100-UUID cap, mutual exclusivity between uuid and tenant filters, cursor pagination, or whether missing UUIDs cause errors rather than partial results.

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?

A single front-loaded sentence with zero filler, which is structurally clean. However, brevity here is under-specification rather than economy - the sentence stops well short of the information the tool needs.

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?

This tool exposes 15 nested filter parameters, pagination cursors and mutually exclusive filter combinations, with no output schema. Given that complexity, one sentence is inadequate; an agent cannot tell how to pass multiple UUIDs, whether results are ordered, or how paging interacts with filters.

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% across a deeply nested query object, so the schema carries the full parameter burden. The description adds no supplementary meaning, which is the baseline expectation when the schema is this well documented, but it misses the chance to highlight the uuids filter that motivates a batch call.

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?

"Gets details for several users at once" essentially restates the name acronis_fetch_users_batch - fetch users, batch. It never says what a "user" object contains or what distinguishes this from sibling acronis_fetch_user, other than the implicit plurality.

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 when-to-use guidance at all. With siblings acronis_fetch_user, acronis_fetch_tenant_users and acronis_fetch_users_batch available, the description never indicates that batch retrieval by UUID list is the reason to pick this one, nor any exclusion conditions.

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