treeflow_list_backups

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

No annotations are provided, so the description carries the full behavioral disclosure burden. The verb 'Lista' implies a read-only operation, which is helpful, but the description does not disclose additional traits such as whether backups are scoped to a tree, whether any side effects occur, or how results are ordered or returned.

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 sentence with no wasted words. It immediately states the action and the resource, making it easy for an agent to parse quickly.

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 with no output schema, the description and schema provide enough to invoke the tool correctly. It lacks explicit usage context and richer behavioral detail, but the operation is straightforward, so this is a minor 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 100%, so the schema already documents tree_id as 'ID del bot/árbol'. The description does not add extra meaning about this parameter, which is acceptable given the schema handles it, but it also does not enhance the agent's understanding of how tree_id filters backups.

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 uses a specific verb ('Lista') and a clear resource ('respaldos y snapshots de seguridad del bot'), making the tool's function unambiguous. It also naturally distinguishes this tool from its many sibling list tools by naming backups as the target.

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 implies this tool should be used when the agent needs to see existing backups, but it does not explicitly state when to use it over alternatives or mention that it is only for reading backups. No when-not-to-use guidance or sibling comparison is provided.

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