http_form_submit

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

With no annotations, the description carries the full burden. It discloses form-submission behavior, redirect handling, and return values, but does not cover error handling, timeouts, or side effects. It provides basic transparency but lacks deeper behavioral detail.

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 front-loaded with a one-sentence summary, followed by a clean bullet-like parameter list and a return-value line. It is appropriately sized for six parameters, though slightly longer than the leanest examples.

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 exists, so the description's return-value line ('status, headers, body, redirect chain') is essential and provided. All parameters are documented, the purpose is clear, and the tool can be confidently invoked based on the description alone.

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 description coverage is 0%, so the description must compensate. It explains every parameter: url, form_data (with example), method, headers, cookies, and follow_redirects. This fully adds meaning beyond the schema's bare titles.

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 opens with 'Submit an HTML form (simulates browser form POST)', which clearly states the tool's action and target. This distinguishes it from the sibling generic http_request tool, making the purpose unambiguous.

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 via 'simulates browser form POST' and lists method options, but it does not explicitly contrast with http_request or mention when not to use the tool. The context is clear enough for most cases, but excludes no alternatives or exclusions.

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