managed_server_list

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

readOnlyHint=true already tells the agent this is a safe read, so the '[READ]' prefix is redundant. The description does add useful value by enumerating the returned fields, which matters since there is no output schema, but says nothing about volume, pagination, or error behavior.

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?

Two short segments with the purpose front-loaded and no filler. The bracketed '[READ]' tag and the 'Args:' block are slightly mechanical but cost almost nothing.

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?

For a single optional-parameter list tool with no output schema, the description covers the resource, the return fields, and the sole argument's semantics and default. Only the absence of any sibling-routing guidance keeps it from being fully complete.

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 load — and it does: 'target' is defined as a Veeam target name sourced from config, with the explicit default behavior when omitted. This is exactly the clarification the bare schema lacks.

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 ('List managed servers') plus the fields returned (id, name, type, description), so the agent knows exactly what comes back. It does not differentiate itself from the many sibling list tools (proxy_list, repository_list, job_list), but the resource noun is distinct enough to route on.

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 relative to alternatives such as proxy_list or repository_list, nor any prerequisite or exclusion noted. The only usage-like instruction ('omit to use the default') concerns the target argument, not tool selection.

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