pressable_list_backups

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

With no annotations provided, the description carries the burden of conveying the operation's nature. 'Get a list' implies a read-only operation, which is helpful, but it does not disclose additional behavioral details such as pagination, ordering, or whether all backup types are included. For a simple list tool, this is minimally adequate but not rich.

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?

The description is a single concise sentence with no wasted words. It efficiently communicates the tool's purpose.

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 one-parameter list tool, the description is mostly adequate, and since there is no output schema, return details are not required. However, the existence of a closely related sibling (list_site_backups_by_type) means the description should have clarified whether this returns all backup types or a specific subset, which is missing.

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 schema contains a single required 'id' parameter with no description (0% coverage). The description adds some context by saying 'for a specific site', implying the id is a site id, but it does not explicitly define the parameter, leaving room for ambiguity.

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?

The description clearly states the tool 'Get a list of backups for a specific site' with a specific verb and resource. However, it does not distinguish this from the sibling tool 'pressable_list_site_backups_by_type', which also lists backups but by type.

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?

No guidance is provided on when to use this tool versus alternatives such as pressable_list_site_backups_by_type. The description only states what it does, with no context about the relationship to sibling backup tools or when one should be preferred.

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