Read backup metadata and status

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is fully covered. The description adds two genuinely useful facts beyond them: that retained backups remain readable after source cluster deletion, and that authorization follows the cluster name; however, "the same cluster-name authorization" is cryptic (same as what?) and nothing is said about error or not-found behavior. With annotations doing the heavy lifting, this lands at adequate-with-gaps.

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?

Two short sentences, front-loaded with the core purpose, and no filler or repetition of the title. It is compact to the point of being sparse given the undocumented parameters, but nothing written is wasted.

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?

There is no output schema and no param documentation, so the description carries the burden of explaining both return content and identifier semantics; it only gestures at the return ("metadata and status"). The retention and authorization notes partially compensate for the complexity of a get tool, but an agent could still not reliably construct a call or interpret the result from this text alone.

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% and the description adds no parameter meaning whatsoever: it never says whether "backup" is a name, ID, or generated label, what happens when "namespace" is omitted, or how cluster-name authorization interacts with the namespace argument. The only parameter documentation anywhere is the $defs description on NamespaceName, which the description does not build on. For a low-coverage schema this is a clear shortfall against the requirement to compensate.

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 clear verb+resource pair ("Read backup metadata and status") and names the object precisely, so an agent knows this is a single-backup read rather than a list. It does not explicitly differentiate itself from near siblings such as backups_list, backup_drill_get, or control_plane_backups_list, so the agent must infer the get-vs-list distinction from the tool names alone.

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 statement of when to use this tool instead of backups_list or the backup_drill/control_plane backup variants. The one usage-adjacent fact is the retained-backup case after cluster deletion, which is framed as a capability rather than a routing rule, and nothing says what to do if the backup is not found or which of the three parameters is required for which lookup path.

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