backup_object_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, and the '[READ]' tag merely repeats that. The description does add value by specifying what is returned (VMs/agents inside a stored backup), but says nothing about pagination, ordering, empty-backup behavior, or errors for an invalid backup_id.

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?

One front-loaded sentence stating scope, followed by a compact two-entry Args block. No filler, no restating of the tool name, and the return entity is named immediately.

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 simple read-only list tool with no output schema, the description identifies the returned entities and both inputs, which is close to sufficient. It omits any mention of result shape or volume (e.g., whether all objects are returned at once), leaving a small gap.

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 documents both parameters: backup_id as a Veeam backup id sourced from backup_list, and target as a Veeam target name from config. It lacks format/example details and doesn't clarify what happens when target is omitted (default null), so it stops short of full coverage.

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 the protected objects (VMs/agents) inside a stored backup'), and the phrase 'inside a stored backup' distinguishes it from the sibling backup_list, which enumerates backups rather than their contents. An agent can pick between the two without opening either schema.

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?

The description points to backup_list as the source of backup_id ('see backup_list'), which implies the tool is used after listing backups to drill into one. However, it never states when to use this versus backup_object_storage_usage or backup_storage_ranking, nor any exclusions or prerequisites.

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