elster_form_check

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

With no annotations, the description carries the full burden, and it delivers the key behavioral fact that the operation is non-mutating ('Never sends') plus the shape of the return value (ok, headline, error panel with causing pages). It omits any mention of auth/session requirements or latency, keeping it short of a 5.

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 tightly packed clauses covering action, return shape, and the critical no-send guarantee, with no filler and the primary action front-loaded.

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?

Because there is no output schema, the description usefully enumerates what comes back and flags the non-mutating behavior, which is exactly what an agent needs. It could add a note about what 'ok' vs an error panel implies for next steps, but it is otherwise complete.

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?

Zero parameters, so there is nothing to disambiguate; baseline for a no-parameter tool is 4.

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 and resource ('Runs ELSTER's "Prüfen" on the open form'), which is unambiguous and clearly distinct from siblings like elster_form_save, elster_form_press, or the submission tools.

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 phrase 'on the open form' implies a prerequisite (a form must already be open), and 'Never sends' hints this is the pre-submission validation step. However, it never explicitly says when to use this versus elster_form_save, elster_form_review, or elster_form_press, leaving the agent to infer.

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