Get Backup Execution

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds the 'reveal' parameter behavior (audited, redacted values) which is useful, but overall does not significantly expand beyond annotation-provided context. No contradiction with annotations.

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 that immediately conveys the core function. It is front-loaded with the verb 'Get' and specifies the resource and identifier. No extraneous information.

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?

Given the simple read operation and rich annotations (readOnly, idempotent), the description is mostly complete. However, there is no output schema and the description does not hint at the response structure (e.g., fields returned, success/error handling). Adding a brief note on return format would increase completeness.

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 coverage is 100%, so all 5 parameters are documented in the input schema with descriptions. The tool description does not add any additional parameter-level detail beyond what the schema provides. Baseline score of 3 is appropriate.

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 states 'Get a single backup execution by its UUID.' with a specific verb ('Get'), resource ('backup execution'), and identifier method ('UUID'). It is distinct from the sibling 'list_backup_executions' which retrieves multiple executions. The purpose is unambiguous.

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 usage when a single backup execution's details are needed, but it does not explicitly mention when not to use it or alternatives like 'list_backup_executions'. The context signals show 'list_backup_executions' is a sibling, but the description provides no guidance on choosing between them.

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