acronis_fetch_applications_issue_statistics

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

The readOnlyHint annotation already establishes this is a safe read, so the description's only job is added context — and it supplies none. It does not say what grouping dimension is used, whether counts are aggregated across all policies or only filtered ones, or how the links_and_issues query option affects 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 eight-word sentence with zero padding and the key concept front-loaded. It is efficient, but for a tool with a nested query object and aggregation semantics it is arguably undersized rather than appropriately sized.

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?

There is no output schema, the parameters are nested, and the tool performs aggregation, yet the description never explains the shape of the returned statistics or what counts as an issue. An agent can guess it is a read-only count query but not what it will receive.

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% and the nested query object documents policy_id, context_id, and links_and_issues in detail, so the baseline of 3 applies. The description adds no filtering semantics of its own, leaving all parameter meaning to 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 names a verb ("counts") and a resource ("problems with applied policies"), which is more than a tautology. But "problems" and "grouped by issue" are never defined, so an agent cannot tell what an issue is or how this differs from siblings like acronis_fetch_application_statuses_by_policy or acronis_fetch_policy_applications.

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 prerequisites, and no mention of any alternative tool. The agent must infer from the name alone that this is an aggregation view rather than a listing of application results.

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