fill

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

With no annotations, the description carries the full burden. It usefully discloses that submit runs only after success ('skipped if any field failed'), but says nothing about partial-failure behavior for fields, permissions/auth needs, or what the call returns on error.

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 dense sentences, front-loaded with the batch promise and followed immediately by the field-shape cheat sheet. Nothing is padded or redundant.

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 or annotations exist, so the description must carry the load; it covers the field shapes and submit behavior well, but leaves return values and error/partial-failure outcomes unspecified.

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 67%, and the description adds genuine meaning by mapping field shapes ('{ref, text} for inputs, {ref, value} for <select>, {ref, check} for checkbox/radio') that the schema's item properties do not explain. It also clarifies the skip-on-failure semantics of submit.

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 ('Fill a whole form') and the key differentiator 'in ONE call', which separates it from the single-field siblings type/select. It never names those siblings explicitly, so the differentiation is implied rather than stated.

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 'all refs from the same snapshot' constraint hints at when this batching is valid, but there is no explicit when-to-use guidance versus type/select/click, and no stated preconditions such as needing a prior snapshot.

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