Remove a saved login

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful scoping context (a site can be a domain or a page URL), but says nothing about whether removal is permanent, whether a domain removes logins for all URLs on it, or what happens when no login exists.

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?

A single front-loaded sentence with no filler; the scope clarification is packed into a parenthetical rather than bloating the text.

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 one-parameter, no-output-schema tool whose annotations already convey destructiveness and idempotency, the description covers the essentials. The only meaningful gap is the domain-vs-URL removal scope.

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 carry the param meaning and it does: "site" accepts either a domain or a page URL on it. What remains unclear is whether passing a page URL forgets only that login or all logins for the domain, which limits it below a 5.

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 ("Forget") and resource ("the person's saved login to a site"), so an agent immediately understands this is a removal operation on stored credentials. It does not explicitly name the neighboring tools (import_login, list_logins) it should be chosen against, but the verb is unambiguous.

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?

There is no guidance on when to use this versus import_login or list_logins, nor any prerequisite such as authentication or the login needing to already exist. Usage is only inferable from the verb.

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