skill_fill_form_workflow

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

The description claims 'filling in a form' which implies writing/mutation, but annotations declare readOnlyHint=true and idempotentHint=true, contradicting the implied behavior. This is a serious inconsistency.

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?

The description is a single concise sentence, but it may be too brief, lacking essential details. It earns a 4 for efficiency but not 5 due to insufficient informativeness.

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?

For a workflow tool with no output schema and complex behavior (filling forms across screens), the description lacks details on expected outcomes, prerequisites, or step-by-step behavior, making it incomplete.

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 single parameter 'form_description' is fully described in the schema (coverage 100%), and the description adds no additional meaning 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?

The description clearly states it is a procedure for filling a form on screen, contrasting with sibling tools like 'skill_type_text' which are lower-level. It uses a specific verb and resource, but could be more precise about what constitutes a '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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it differs from individual input tools.

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