Delete Auth Context

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

The description discloses that deletion also removes the storage state file, which is useful behavioral context beyond the title. However, it does not state whether deletion is permanent or affects active sessions, and with no annotations available, the description carries the full burden without fully addressing these aspects.

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 sentence of 11 words, front-loaded with the verb and object. Every word earns its place, with no redundant 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 single-parameter delete operation, the description covers the core action and an important side effect (deleting the storage state file). The presence of an output schema covers return values. However, given the destructive nature and lack of annotations, a brief note on irreversibility or impact on existing sessions would make it more 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?

The input schema provides only 'authContextId' with no description, and schema description coverage is 0%. The tool description does not mention the parameter or explain how to obtain or use the authContextId, so it adds no meaning beyond the field name.

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 uses the specific verb 'Delete' and clearly identifies the resource as a 'saved auth context' and its 'storage state file'. This distinguishes it from sibling tools like save_auth_context, load_auth_context, and list_auth_contexts.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, situations where deletion is appropriate, or when to prefer other auth context tools.

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