delete_authentication_from_user

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

The description only states 'Remove an authentication from a user', which aligns with the destructiveHint annotation. However, it adds no additional behavioral context (e.g., what happens if the authentication is the last one, or if it's linked to other records). The annotation already covers the destructive nature, but the description should provide more insight.

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 with no fluff. It is concise and to the point, though it could be slightly expanded to include usage context without sacrificing brevity.

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?

Given the tool has no output schema and annotations already provide destructive and idempotent hints, the description is minimally complete. However, it does not explain the result of a successful deletion or any side effects, which would be helpful for an agent.

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 already fully describes both parameters with 'ID of the parent resource' and 'ID of the authentication to delete'. Since schema coverage is 100%, the description does not need to add parameter details, but it also does not provide any extra meaning beyond what is in the schema.

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 clearly states the action ('Remove') and the resource ('authentication from a user'). It is specific enough to convey the tool's purpose, but does not differentiate from sibling deletion tools like 'delete_affiliation' or 'delete_comment'.

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 (e.g., when to delete an authentication vs. update it). No exclusion criteria or prerequisites are mentioned.

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