deployado_list_backup_targets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the account-scoping detail; it says nothing about result ordering, empty-list behavior, or that the returned targets feed run_backup/restore_backup.

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 front-loaded sentence with no filler. The resource and scope land in the first few words, which is exactly what an agent scanning candidates needs.

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 no-parameter read tool with annotations covering safety, the description is minimally sufficient. It is incomplete in that it does not say what the targets are used for downstream (backups/restores) or how they relate to the create/get/run backup siblings in the same namespace.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not promise any filtering options, which matches the empty schema and avoids misleading the agent.

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 backup targets) and scopes it to 'configured for your account', which distinguishes it from deployado_get_backup_target. However, it never names or contrasts with the obvious sibling that fetches a single target, so a reader must infer the relationship.

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?

Usage is implied by the name and the word 'all' — this is the enumerate-everything variant — but the description gives no explicit when-to-use / when-not-to-use guidance and does not point to deployado_get_backup_target for details or deployado_create_backup_target for adding one.

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