elster_ustva_start

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

No annotations provided, so the description carries full burden. It discloses the full workflow (opens browser, logs in, fills form, runs Prüfung, pauses), the required confirm step, and the return value. It omits error handling, auth details beyond login, and rate limits.

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?

Three sentences/fragments, front-loaded with the core action and the critical pause constraint. No wasted words.

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?

Given no output schema and no annotations, the description covers the key workflow, the pause/confirm handshake, and polling. It lacks failure-mode guidance, but is otherwise complete for a multi-step session starter.

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 75%; the description adds no parameter meaning. The schema already documents period, report, and takeover, but 'year' remains undocumented in both schema and description.

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 ('Starts a UStVA submission session') and distinguishes from the confirm sibling by describing the pause point. Clearly differentiated from other start tools (eur_start, est_start) via the UStVA qualifier.

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?

Explicitly names the follow-up call (elster_ustva_confirm) required to send, and the status-polling alternative (elster_session_status). Does not state when to prefer this over other form tools or prerequisites beyond login.

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