Delete a saved login

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

Annotations already declare destructiveHint=true, so the safety profile is covered; the description adds the important detail the annotations cannot convey — that omitting username escalates a targeted delete into a bulk removal of all logins for the origin. It also discloses that a removal count is returned. It does not state irreversibility or whether password data is recoverable, which keeps it at 4.

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?

Three short sentences, front-loaded with the action, then the parameters, then the return behavior. Nothing is padded and each sentence carries a distinct fact.

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?

With no output schema, the description usefully covers the return value (a removal count) and fully explains the destructive scope. For a two-parameter tool with annotations already flagging destructiveness, that is close to complete; only recovery/permission caveats are absent.

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 coverage is 100% and both parameters already carry descriptions including the 'default: all' behavior, so the description is largely restating the schema. It reinforces the omission semantics but adds no format or syntax guidance beyond that. Baseline 3 applies.

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 and resource ('Delete saved logins') that is unmistakably distinct from the sibling read/write login tools (browser_list_logins, browser_add_login, browser_get_login_password). It also clarifies the bulk-vs-single scope, which no sibling name implies. It stops short of naming an alternative tool, so it lands at 4 rather than 5.

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?

Explains the key selection decision the agent faces: supply username to target one entry, omit it to wipe every login for the origin. That is real when-to-use guidance for the tool's main branching point. No exclusions or prerequisite steps (e.g. verifying with browser_list_logins first) are stated.

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