acronis_fetch_user

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that, the description says nothing about the allow_deleted behavior, what happens with invalid or nonexistent IDs, or whether deleted users are returned by default – all of which matter for correct invocation.

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?

The single sentence is front-loaded and free of filler, but it is undersized for a tool with two parameters and several near-neighbor siblings. Being brief is fine, yet here brevity edges into under-specification rather than efficient signal.

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 is a simple read tool with full schema coverage, annotations covering safety, and no output schema to explain, so a short description is defensible. Still, the absence of any note on the allow_deleted flag's effect or on sibling disambiguation leaves the agent with gaps it must fill itself.

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 both the user_id UUID and allow_deleted flag are already documented in the schema. The description adds no parameter meaning beyond the schema, which is acceptable at baseline 3 but offers no extra value.

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?

The description states a specific verb and resource ('Fetches a user by ID'), which is clear and unambiguous. It does not differentiate from sibling tools such as acronis_fetch_users_batch, acronis_fetch_tenant_users, or acronis_fetch_current_user_info, so an agent must infer from the name which path to take.

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 alternatives (batch fetch, tenant users, current user), and no stated preconditions such as required ID format or permissions. The 'by ID' phrasing weakly implies a lookup, but nothing is explicit.

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