anmeldedaten_entfernen

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

With no annotations, the description carries the full burden. It states the action 'deletes' but does not disclose irreversibility, permission requirements, or whether it affects active sessions. The description is terse and lacks additional context that would inform an agent about side effects.

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, concise sentence that directly conveys the tool's action and target. It is appropriately sized with no redundant words or filler.

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 simple delete operation with one parameter, the description gives the essential action. However, it lacks context on side effects or usage, and because there are no annotations, the overall guidance is minimal. The presence of an output schema reduces the need to describe return values.

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. It does not explain what 'portal_id' refers to or how to obtain it. The schema title 'Portal Id' is minimally descriptive, but the description adds no value beyond that.

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 uses a specific verb 'Loescht' (deletes) and a clear resource 'hinterlegte Anmeldedaten eines Portals' (stored login data of a portal). It clearly distinguishes from sibling tools like 'anmeldedaten_hinterlegen' (store credentials) and 'portal_sitzung_loeschen' (delete session).

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?

No guidance is provided about when to use this tool instead of alternatives. It does not mention prerequisites, such as needing an existing portal_id, or contrast with sibling operations like storing or updating credentials. Usage context must be inferred.

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