delete_password

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does mention that a JSON string deletion confirmation is returned, but it does not note that deletion is permanent, whether permissions are required, or whether related references are affected. For a destructive tool, this is thin.

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 compact and front-loaded with a clear purpose sentence, followed by scannable Args and Returns sections. The Args block is somewhat redundant with the schema, but the structure is efficient and easy to parse.

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 destructive tool this is minimally adequate: the agent knows the action, the required parameter, and that a deletion confirmation is returned, with an output schema also present. It lacks warnings about permanence or operational caveats that would make it fully 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?

Schema description coverage is 0%, so the description must compensate. The line 'password_id: The IT Glue password ID' adds minimal context beyond the schema's 'Password Id' title but gives no format, source, or validation details. It is sufficient for a simple integer ID, but no more.

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 specific verb ('Delete') and resource ('password entry') scoped to IT Glue, making it unambiguous among the many delete_* siblings such as delete_contact, delete_document, and delete_location. The purpose is immediately clear.

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 gives no explicit comparison to alternatives like update_password or create_password, and no when-not-to-use guidance. The only signal is the implied use case: when a password entry needs to be removed.

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