elster_ustva_start

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

With no annotations, the description fully discloses behavioral traits: opens a browser, logs in, fills form, runs Prüfung, pauses at AWAITING_CONFIRM, and returns a sessionId. It does not mention authorization or rate limits, but the core behavior is well-covered.

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?

Two sentences, front-loaded with critical sequence of actions. No wasted words; every sentence adds value.

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 the tool's complexity (multi-step, no output schema), the description is fairly complete: explains the workflow, return value, and next steps. Minor gap: no mention of error handling or prerequisites (e.g., existing config).

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 ~67%, so the schema already documents most parameters. The description does not add additional meaning beyond listing the parameters (year, period, report). Adequate but not enhanced.

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 starts a UStVA submission session, detailing the sequence of actions (opens browser, logs in, fills form, runs Prüfung, pauses). It distinguishes from sibling tools like elster_ustva_confirm by noting the session pauses and requires a confirm call.

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 states when to use (to start a UStVA submission) and what not to do (must call elster_ustva_confirm to send, poll status via elster_session_status). Provides clear context for alternative tools.

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