acronis_fetch_categories

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds almost nothing beyond that, and its "turned on" framing actually understates the tool's behavior since the schema exposes an include_disabled option — a conflict the description never reconciles.

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 short sentence with no wasted words, which is good, but the brevity tips into under-specification rather than tightness — there is no return-shape or scoping detail to anchor it.

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?

With no output schema, the description must at least indicate what a "category" contains (id, name, enabled flag) for the agent to use the result, and it does not. Combined with the missing sibling differentiation, it leaves real gaps for a tool sitting among 30+ alert/tenant siblings.

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 include_disabled is already fully documented with its effect. The description does not mention the parameter at all, and its "turned on" wording slightly contradicts the option to include disabled categories, so it adds no meaning 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?

The description gives a verb and resource ("Lists the alert categories") plus a scope qualifier ("turned on"), so the basic operation is inferable. However, it never distinguishes itself from the near-identical sibling acronis_fetch_all_alert_types, and the phrase "turned on" is ambiguous about whether it means enabled categories or categories with active alerts.

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 guidance on when to call this versus acronis_fetch_all_alert_types or the other alert-related siblings, and no stated prerequisites or exclusions. The agent must infer the distinction from the tool name alone.

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