List backup drills

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered elsewhere. The description contributes nothing about ordering, whether results span all namespaces by default, or how the cursor behaves, which are the traits an agent actually needs here.

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 single four-word sentence is not concise in the useful sense — it is under-specification. There is no front-loaded statement of scope or behavior because there is no content at all beyond the name.

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 paginated, cluster-scoped list tool with no output schema and zero parameter documentation, the description omits everything an agent needs: default scoping when namespace is omitted, pagination termination, and result shape. This is essentially a bare stub.

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 0%, so the description carries the full burden for four parameters and provides none of it. Only 'cluster' is required, yet nothing explains whether omitting 'namespace' lists across all namespaces or whether 'limit'/'cursor' form a resumable pagination loop — the parameter names alone are only partially self-explanatory.

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?

Tautological: description restates name/title.

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 when-to-use guidance is given: nothing says to use this to enumerate drills across a cluster/namespace versus calling backup_drill_get for a specific drill. There are no stated preconditions, no mention of pagination workflow, and no exclusions.

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