elster_est_start

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

With no annotations, the description covers key behaviors: it fills data, runs a check, waits 30 minutes, and explicitly states it never submits. However, it does not mention rate limits, authentication needs, or what happens if a session already exists. The blocking wait is mentioned but not elaborated.

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, no fluff. First sentence states purpose, second details steps and the constraint. Information is front-loaded and efficient.

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?

Despite low complexity (2 params, no output schema), the description omits important details like return value, how to check session status, and prerequisites. It mentions a 30-minute wait but doesn't clarify if the function blocks or returns immediately. Leaves significant gaps for an agent.

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 description adds value for the 'data' parameter by explaining matching by substring and the use of empty object. The 'year' parameter is left without explanation beyond the schema. With 50% schema coverage, the description partially compensates.

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 that the tool starts an ESt 1 A form-prep session, detailing the steps: opens form, fills taxpayer basics, runs Prüfung, waits 30 minutes, and never submits. This distinguishes it from siblings like elster_ustva_start (sales tax) or elster_eur_start (another form).

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for pre-submission preparation, but lacks prerequisites like needing an active session or instructions on when to call this tool over session management tools.

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