overview

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

readOnlyHint=true already tells the agent this is a safe read, and the '[READ]' tag reinforces it. The description adds value beyond annotations by disclosing the actual payload of the summary (job results, capacity warnings, active sessions), which matters since there is no output schema. It does not cover scoping/limits of the aggregate, so not a 5.

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?

Front-loaded purpose, then a one-line usage directive, then a compact Args block. Every sentence earns its place and there is no repetition of schema content.

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 compensates by naming the three summary sections it returns, and it explains the single parameter. It stops short of describing granularity or limits of the aggregate, but it is complete enough to call correctly.

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 0%, so the description must carry the param, and it does: 'target: Veeam target name from config; omit to use the default' explains origin and default behavior. It does not describe accepted formats or errors for an unknown target, leaving a small gap.

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+resource ('one-shot health summary') and enumerates exactly what it summarizes: jobs by last result, repos near full, running sessions. This clearly distinguishes it from the drill-down siblings (job_get, repository_get, session_get).

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?

Explicitly says 'Call this first to triage a Veeam environment before drilling into a specific job, repository, or session,' which gives both the ordering ('first') and the alternative path (per-entity drill-down tools). Nothing is left to inference.

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