acronis_fetch_tenants_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; the description adds that multiple tenants are returned in one call and that subtree mode means 'everything under it'. It says nothing about pagination, result limits, deleted-tenant handling, or what fields come back, which the schema covers only indirectly.

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 the core verb and resource first and no wasted preamble. The trailing phrase 'as a tenant and everything under it' is slightly awkward relative to the schema's subtree_root_id terminology.

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 read-only query tool with no output schema and a deeply nested parameter object containing three mutually exclusive selectors plus cursor pagination. The description covers the selection modes but leaves out pagination behavior, the level-of-detail concept, and default scoping, so it is only minimally complete for this schema's complexity.

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 the nested parameters are already fully documented, giving a baseline of 3. The description groups uuids, parent_id, and subtree_root_id into three modes, which lightly reinforces their mutual exclusivity but adds no format or constraint detail beyond the schema.

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 ('Gets several tenants at once') and names the three selection modes (UUID batch, parent tenant, subtree). It does not differentiate itself from near-siblings such as acronis_fetch_tenant or acronis_fetch_tenant_children, whose scope overlaps with the parent_id and subtree_root_id modes.

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?

The sentence enumerates the mutually exclusive selection modes but gives no explicit when-to-use or when-not-to-use guidance, and never names an alternative tool. An agent facing both this tool and acronis_fetch_tenant_children has to infer the difference from the schemas.

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