decrypt_backup

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

With no annotations, the description covers the binary format, passphrase handling (never stored), default output location, and return value. It lacks details on error conditions but is fairly comprehensive.

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 front-loaded with the core action, then provides format details and Args list. Each sentence serves a purpose, no wasted words.

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 3 params with no schema descriptions and an output schema, the description fully explains inputs, outputs, behavior, and format. No obvious gaps.

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?

Since schema coverage is 0%, the description's Args section adds meaning by briefly explaining each parameter's role (enc_path, passphrase, output_path). Could be more detailed but adds value.

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 explicitly states the tool decrypts .enc backups from encrypt_backup, provides the file format, and explains the output behavior. It clearly identifies the action and resource.

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 indicates this is the counterpart to encrypt_backup for restoration, but does not explicitly state when not to use it or compare to other restore tools like restore_db. Clear context without exclusions.

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