elster_form_page

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 does disclose the key safety trait ('Read-only.') and describes the return shape in useful detail, but omits pagination semantics, authentication/prerequisite state, and any limits or 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?

Front-loaded with the core action, then the RID mechanic, then the return contents in a single dense paragraph. Every clause carries information, though the parenthetical RID example is long and slightly heavy.

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?

With no output schema and no annotations, the description does the heavy lifting by enumerating what is returned (plain fields, repeat groups, non-navigation commands, validation errors, nav RIDs), which is sufficient for an agent to invoke and interpret the call.

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 coverage is 0% and the single rid parameter is undocumented in the schema, but the description compensates well: it gives a concrete RID example, explains the format ('FormData://...'), notes the source ('the nav list of any page'), and implies rid is optional ('jumps there first').

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+resource: 'Reads a page of the open form,' and elaborates on the exact payload (fields, repeat groups, commands, validation errors, nav RIDs). It does not explicitly differentiate itself from siblings like elster_form_crawl or elster_form_check, so it stops short of a 5.

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 ('a page of the open form') and explains that passing rid jumps there first, but never states when to prefer this tool over elster_form_crawl, elster_form_check, or elster_form_review. Usage is inferable rather than explicit, and no when-not conditions or alternatives are named.

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