Remove Stored Credentials

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

Annotations indicate destructiveHint=true, idempotentHint=false. Description elaborates on the destructive nature with 'preview-first' pattern, explaining that default is non-destructive preview and explicit execute is needed for deletion. No contradiction; adds valuable context beyond annotations.

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 sentences, front-loaded with purpose and workflow. Every phrase adds value: 'preview-first', 'preview and remove', 'call again with execute=true.' No filler or redundancy.

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 the core workflow and critical parameters. Lacks details on error handling or side effects, but given schema and annotations, it's sufficient for correct invocation. No output schema, but description mentions returned plan_handle.

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% with parameter descriptions. Description adds workflow context linking parameters: 'returns a plan_handle; call again with execute=true and that handle.' This enhances understanding beyond schema alone, especially for the execute and plan_handle interplay.

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?

Description clearly states the tool's purpose: 'Preview and remove one stored credential block from a local/global .env file.' It specifies both preview and removal actions, the resource (credential block in .env), and scope (local/global). No sibling tool duplicates this function.

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 guidance on the two-step workflow: 'the default call projects the removal and returns a plan_handle; call again with execute=true and that handle to delete.' This clarifies when to use execute versus preview. However, it does not mention when not to use or alternatives, so slightly less than perfect.

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