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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's real contribution is disclosing the response shape (label, coverage, storage, type, frequency, size, status) and the underlying endpoint GET /backups. That is genuinely useful given there is no output schema, though pagination behavior is left to the schema.

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?

Three short sentences, information-dense and front-loaded: resource first, returned fields second, filters third. The opening fragment 'The backup instances of the workspace' is telegraphic but costs nothing in length.

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 read-only list tool with no output schema, the description does the minimum needed by enumerating return fields, and pagination is handled by the schema. The notable gap is that it never distinguishes this tool from runcloud_list_backup_snapshots, leaving real ambiguity in a 40-tool sibling set.

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 every parameter is already documented in the schema, which sets the baseline at 3. The description's filter mention (server, storage, status, name) maps onto server_id, storage, status and search but adds no syntax or format detail beyond what the schema already provides.

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?

It names a specific verb (list) and resource (backup instances of the workspace) and even enumerates the fields returned, so an agent knows exactly what comes back. What it does not do is distinguish itself from the sibling runcloud_list_backup_snapshots, which an agent could easily confuse with this tool.

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?

It states the available filters (server, storage, status, name), which implies the retrieval use case, but gives no when-to-use guidance, no prerequisites, and no exclusion pointing to runcloud_list_backup_snapshots as the alternative for snapshot data. Usage 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.