iyke_secret_delete

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

Discloses that operation is destructive, idempotent (ok for missing key), and does not affect legacy unscoped key. However, no mention of permissions, side effects, or rate limits. With no annotations, description carries burden and does a good job but not exhaustive.

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?

Two concise sentences with no filler. Front loads the core action, then adds important details (idempotency, legacy behavior). Every sentence earns its place.

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?

Covers core behavior and idempotency, but lacks parameter documentation for scope and key. No output schema, but description hints at return behavior. Could be more complete by explaining scope semantics inline.

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 has 0% description coverage for parameters. Description mentions 'scope' but does not explain its semantics or allowed values, only references another tool. 'key' is described only as the secret key implicitly. Minimal added value beyond schema itself.

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?

Clearly states 'Delete a secret from the given scope' and distinguishes from siblings by noting it does not touch legacy unscoped key, providing specific verb+resource+scope.

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?

Explicitly says when to use (delete a secret), notes idempotent behavior (returns ok even if key missing), and gives direct guidance on cleaning up legacy entries by deleting at unscoped key directly.

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