sops_delete_secrets

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

With no annotations, the description discloses key behavioral traits: removal of both encrypted value and metadata entry, rejection of dependent keys unless included in the delete list, and the required environment variable. It lacks explicit output details but covers important safety and dependency behavior.

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 three sentences with no fluff. It front-loads the main action, then provides specific removal details, and ends with a crucial constraint. Every sentence adds necessary 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?

For a tool with 2 parameters and no output schema, the description covers the deletion process, dependency rule, and env var requirement. It does not describe the return value or error scenarios beyond dependency rejection, but given the context, it is largely complete.

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 baseline is 3. The description adds value by explaining the effect on parameters: it clarifies that deleting a key removes its encrypted value and meta entry, and that key_names may be rejected if dependencies are not also deleted. This goes beyond the schema descriptions.

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 clearly states the tool deletes keys from a SOPS-encrypted file, with specific details about what is removed (encrypted value and _meta_unencrypted entry). It distinguishes itself from sibling tools like sops_add_secrets or sops_list_secrets by specifying deletion behavior and dependency handling.

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 when to use (deleting keys) and includes a prerequisite (requires SOPS_AGE_KEY env var). However, it does not explicitly contrast with alternatives or provide when-not-to-use scenarios, though the dependency rejection provides a constraint.

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