delimit_secret_revoke

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

No annotations present, so description fully discloses side effects: writes a revocation record via ai.secrets_broker.revoke_secret, subsequent get calls denied, access log preserved. Provides clear behavioral expectations.

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?

Description is concise (4 sentences) and well-structured with labeled sections for when to use, when not to, sibling contrast, and side effects. Every sentence adds value.

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 simple revoke tool with one parameter and an output schema, the description covers use cases, side effects, and parameter usage completely. No gaps identified.

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 tool description does not add meaning beyond the input schema for the single parameter 'name'. Schema coverage is 100%, so baseline 3 is appropriate; the description repeats 'Required.' which is already in the parameter description but does not provide additional semantics.

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 verb 'revoke' and resource 'secret' with the purpose 'prevent any future access'. It contrasts with sibling tool delimit_secret_store, which 'creates', and implicitly distinguishes from delimit_secret_get by noting revocation blocks it.

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?

Provides explicit when-to-use scenarios ('after a credential leak or when rotating away from an old secret name') and when-not-to-use ('to delete metadata only — revocation also blocks delimit_secret_get'). Includes sibling contrast for alternatives.

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