Bankid Login Start

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

Annotations already disclose readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this initiates an external, non-destructive flow. The description adds the mode semantics but omits the operationally important trait: that this only opens a session and must be followed by polling, plus any expiry/timeout behavior.

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 sentence with the scope constraint front-loaded and the two enum meanings packed in with zero filler. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and the sole parameter is fully covered. The remaining gap is the interaction lifecycle — that this pairs with bankid_login_poll — which an agent must infer from sibling names.

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 0%, so the description must carry the parameter meaning, and it does: 'qr' is explained as scanning from another device and 'app' as this device, which is meaning the bare enum cannot convey. It does not restate the default of 'qr', but that is minor.

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+resource ('start a BankID login') and scopes it with 'Login panel only', which together with the sibling name bankid_login_poll makes the start-vs-poll split readable. It stops short of naming the sibling explicitly, so it's clear but not maximally differentiated.

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?

'Login panel only' implies the context where this applies, and the start/poll naming suggests a follow-up, but the description never says 'call bankid_login_poll afterwards' or when not to use this tool. Usage is left to inference from the name pair.

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