Bankid Login Poll

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds that the tool surfaces login status and a QR code, but it does not disclose polling behavior, rate limits, QR expiry, or session lifecycle details that would matter for an open-world login flow.

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 short sentence with no wasted words. It is appropriately sized, though the fragment style ('Login panel only:') is a bit terse and does not front-load the action as clearly as a complete sentence would.

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?

With an output schema and rich annotations, the description does not need to explain return values or safety profile. However, for a polling tool that has a sibling 'bankid_login_start', the description is incomplete about when and how to use this tool in the overall login flow.

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?

The tool has zero parameters, so there is nothing for parameter semantics to document. The baseline score of 4 is appropriate.

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 provides current login status and a QR code, which combined with the name 'poll' gives a specific resource and implied action. However, it does not distinguish this from the sibling 'bankid_login_start' or explicitly say it polls an ongoing login 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?

The phrase 'Login panel only' gives a UI scope but does not explain when to call this tool versus 'bankid_login_start', how often to poll, or what conditions indicate completion. No when-to-use or when-not-to-use guidance is provided.

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