auth_delete_profile

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

With no annotations provided, the description carries the full behavioral burden. It clearly discloses the object being destroyed and the side effect of removing the saved session, but it does not add caution about irreversibility, required permissions, or post-deletion consequences.

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?

One short, well-structured sentence that front-loads the destructive verb and includes the key side effect with zero filler. Every word 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?

The tool is low-complexity: one required string parameter and no output schema. The description is sufficient for basic invocation, but a brief note on irreversibility or naming expectations would make it more complete for safe and correct use.

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 only required parameter, `name`, has zero schema description coverage and is never mentioned in the description. The description only vaguely implies that `name` refers to an auth profile, leaving the agent to infer format, existence requirements, or how to discover valid names.

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?

States a precise action (`Delete`) on a specific resource (`auth profile`) and explicitly names what will be removed (`saved session`). This distinguishes it from sibling auth tools like `auth_update_profile` or `auth_check` by the unique destructive 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?

Gives no guidance on when to prefer this tool over alternatives such as `auth_update_profile`, `auth_profiles`, or `auth_import_storage_state`. No prerequisites, exclusions, or conditions for use are mentioned; the intended use is only implied by the verb 'Delete'.

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