secretsmanager_restore_secret

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

With no annotations provided, the description must fully disclose behavioral traits. It only restates the basic action ('Restore a previously deleted secret') without mentioning side effects, permission requirements, or whether the operation idempotent or reversible. This is a significant gap for a mutation tool.

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, concise sentence that front-loads the verb and object. It contains no unnecessary words or redundant information, earning full marks for efficiency.

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?

The tool has a simple signature (one required param) and no output schema, but the description lacks contextual nuances such as behavior for already-restored secrets or permanent deletion, which would be important for an agent to invoke correctly. It is adequate but leaves key details unaddressed.

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?

The schema has one parameter (secretId) with a clear description ('Secret name or ARN'), providing 100% schema coverage. The description adds no additional parameter meaning beyond what the schema already provides, so the 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 clearly states the action ('Restore') and the resource ('previously deleted secret in Secrets Manager'), making it distinct from sibling tools like secretsmanager_delete_secret or secretsmanager_create_secret. It identifies the specific operation and scope without ambiguity.

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 the use case: restoring a previously deleted secret. However, it does not explicitly state when to use this tool versus alternatives (e.g., create_secret) or mention any prerequisites or exclusions (e.g., permanently deleted secrets cannot be restored).

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