anmeldedaten_hinterlegen

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable security context: credentials are encrypted using Fernet and plaintext is never logged. However, it does not disclose whether the tool is idempotent, what happens on duplicate portal IDs, or any required permissions. This is a partial but meaningful transparency effort.

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 exceptionally concise—two short clauses in German. Every word contributes meaning: 'hinterlegt' (stores), 'verschluesselt' (encrypted), 'Fernet' (algorithm), and the no-logging guarantee. There is no fluff, and the structure is front-loaded with the action.

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?

This is a mutation tool with no annotations and a very brief description. While an output schema exists (so return format is not needed), the description omits critical context such as whether the operation overwrites existing credentials, how to handle errors, or what side effects occur. For a 3-parameter tool, the description is too sparse to be fully actionable.

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%, and the description adds no parameter-level information. The parameter names (passwort, portal_id, benutzername) are somewhat self-explanatory, but the description does not explain formats, constraints, or relationships between parameters. It fails to compensate for the lack of schema descriptions.

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 identifies the action ('Hinterlegt Anmeldedaten' = stores login data) and the resource, which distinguishes it from the sibling 'anmeldedaten_entfernen' (remove). However, it does not specify whether this creates or updates existing credentials, and the verb 'hinterlegen' is slightly generic, so it is not a 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., portal ID must exist) or scenarios where this is preferred over portal_login or other siblings. No exclusions or alternative tool references are given.

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