elster_datenuebernahme_list

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

No annotations provided, so the description carries the full burden. It usefully states 'Read-only' and 'without starting a filling session', covering the main behavioral trait. However, it omits details on permissions, rate limits, or other side effects.

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 the core action and scoping constraint. Every sentence earns its place by guiding the agent to the downstream usage.

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?

No output schema exists. The description implies the return contains an 'aufgabeId' or year, which is helpful, but does not fully describe the list's structure or pagination behavior. Adequate for a simple two-parameter list tool.

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 100%, so the schema already documents both parameters. The description adds the context that 'form' selects which form to inspect and 'year' is the tax year of the new form, but provides no syntax or format details beyond the schema.

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 (Lists), resource (earlier submissions ELSTER offers to carry over), and scope (for a given form and tax year). Explicitly distinguishes from the start tools by saying 'without starting a filling session', allowing an agent to identify it without opening schemas.

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?

Provides clear context: use this to find carry-over data before starting a filling session. Names the downstream tools (elster_ustva_start / elster_eur_start / elster_est_start) and the argument ('takeover') to pass results into. No explicit when-not-to-use, but the alternative path is evident.

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