elster_eur_start

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

No annotations are provided, so the description carries the full burden. It reveals key behaviors: filling up to Prüfung, saving and exiting, and never submitting. This is transparent about the session lifecycle and constraints.

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 two sentences, front-loaded with the action, and contains no extraneous 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 no output schema and a complex procedure, the description explains the internal steps and final state (draft survives). It is missing prerequisites (e.g., active session) but is largely complete for the tool's purpose.

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 schema description covers the 'data' parameter but not 'year'. The tool description does not add meaning for 'year' and merely restates the schema's field list for 'data'. Schema description coverage is 50%, but the description does not compensate for the missing parameter documentation.

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 specifies the tool starts an EÜR form-prep session, fills it up to Prüfung, saves the draft, and explicitly states it NEVER submits. This distinguishes it from sibling start tools like elster_est_start and elster_ustva_start.

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 description implies usage for EÜR form preparation and clarifies the draft-saving behavior. However, it does not explicitly state when not to use it or compare to siblings, though the context is clear enough.

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