clear_credentials

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and return type but does not mention side effects, reversibility, scope of clearing, or any security implications. The phrase 'from session' hints at locality but is vague.

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 extremely concise, with one clear action sentence and a separate return note. It is front-loaded with the core behavior and contains no unnecessary words, making it easy for an agent to process.

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 zero-parameter tool with a simple operation, the description is mostly complete. It states the action and the return value. However, it lacks any explanation of when or why you would clear credentials, and provides no context about related setup/get tools. This is a minor gap given the tool's simplicity.

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 has zero parameters, so the baseline is 4. The description adds no parameter-specific info, but none is needed. It clearly states the operation on stored credentials, which is sufficient for a param-less tool.

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 a specific verb 'Clear' and resource 'stored credentials from session', which precisely defines the action. It distinguishes this tool from siblings like setup_credentials and get_credentials_status by focusing on removal rather than setup or retrieval.

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?

No usage context is provided. The description does not explain when to clear credentials (e.g., after session completion) or contrast with setup_credentials and get_credentials_status. There are no exclusion criteria or alternative recommendations.

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