acronis_fetch_tenant_users

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

readOnlyHint=true already covers the safety profile, and the description adds the useful fact that only UUIDs come back rather than full user records. However, it says nothing about pagination, result limits, or how the nested-tenant and hidden/deleted flags affect output scope, which the schema only partially implies.

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 no filler, and the key distinction (UUIDs only) is placed where it will be read. It is arguably too terse for the tool's scope, but nothing is wasted.

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?

The tool is a simple read with fully documented parameters and no output schema, so the description is close to sufficient. It still omits sibling differentiation and any notion of response size or pagination behavior, leaving gaps an agent would hit in practice.

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 detailed descriptions for order, allow_deleted, include_hidden, and include_grand_children, so the baseline is 3. The description contributes no additional meaning about how tenant_id or the query flags shape the result.

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 ("Fetches a list of UUIDs of the tenant's users") and adds a meaningful qualifier: only UUIDs are returned, not full user objects. It does not distinguish itself from sibling tools such as acronis_fetch_user or acronis_fetch_users_batch, so an agent must infer the split.

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?

There is no when-to-use guidance, no mention of when to prefer acronis_fetch_user / acronis_fetch_users_batch, and no prerequisites. The agent must infer that this is the lightweight bulk-ID lookup versus the detail-fetching siblings.

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