list_operations

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that results are scoped to the selected backend; it says nothing about whether this is read-only (implied by "List" but unconfirmed), whether a backend must be selected first, what happens if none is selected, or what the returned entries look like.

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 or repetition. It is efficient, though its terseness borders on under-specification rather than optimal compression.

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 zero-parameter discovery tool, the description is minimally adequate. With no output schema and no annotations, it should still clarify what a "controlled operation" is and what a caller gets back, since that is the entire value of a list operation.

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 no parameter semantics for the description to add. Baseline 4 applies; the mention of backend scoping is a bonus constraint rather than a parameter explanation.

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 gives a verb ("List") and a resource ("controlled operations supported by the selected backend"), which is more than a tautology. However, "controlled operations" is never defined, and the description does not distinguish this from siblings such as execute_operation, get_operation_status, or list_connections, so an agent cannot tell precisely what is being enumerated.

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?

There is no explicit when-to-use statement and no mention of alternatives. The phrase "supported by the selected backend" hints at a prerequisite (a target must be selected, cf. vault_select_target) but never states it, leaving the agent to infer both the trigger condition and the ordering constraint.

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