portal_login

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

With no annotations, the description bears full responsibility for disclosing behavior. It reveals that the tool opens a visible browser and saves login, but does not clarify whether login is persistent, whether it overwrites existing credentials, or if any setup is required. The mutating nature of 'speichert den Login' is noted, but side effects and reversibility are absent.

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 front-loads the primary action. Every word contributes meaning, with no redundant phrases or irrelevant details.

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 tool with three parameters, no annotations, and minimal description, the context is incomplete. It omits when to use the tool, what 'auto' controls, and expected outcomes beyond opening and saving login. The output schema exists but does not offset the lack of operational guidance.

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?

Input schema has no parameter descriptions (0% coverage), and the tool description does not explain the purpose of 'auto', 'sichtbar', or 'portal_id'. It only loosely maps 'sichtbar' to 'sichtbar fuer den Nutzer' but leaves the other parameters undefined, failing to compensate for the schema's lack of detail.

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 states the tool's function with a specific verb and resource: 'Oeffnet den Portalbrowser sichtbar fuer den Nutzer' (opens the portal browser visibly) and 'speichert den Login' (saves the login). This distinguishes it from sibling tools like browser_status (status only) and anmeldedaten_hinterlegen (storing credentials separately).

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 on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or explicitly say to prefer this over sibling tools like anmeldedaten_hinterlegen. Usage context is only implied by the action described.

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