submit_form

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

With no annotations provided, the description carries the full disclosure burden. It does well: states it returns the result page, rides the user's session (privacy-relevant behavior), and explains the submit fallback behavior. It doesn't address rate limits or destructive potential, but the tool is primarily a form-submission action with benign scope; the session and Enter-fallback disclosures add meaningful value beyond schema.

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 dense and richly informative, with concrete examples and front-loaded purpose. It's somewhat long but every sentence earns its place—covering pipeline, fields mapping, submit behavior, session, and usage guidance. The only mild inefficiency is the slightly repetitive closing paragraph about use cases.

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?

Given 6 params with 0% schema coverage and no annotations, the description covers the core ones well and references the parent pipeline. An existing output schema lightens the return-format burden. It could add a bit more on private/max_chars and error conditions, but for a mid-complexity form tool it's largely 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?

Schema description coverage is 0%, so the description must explain the parameters, which it does well. It explains 'fields' with concrete mapping examples (label→value), clarifies 'submit' semantics and its default fallback (Enter in last field), and for max_chars/wait_selector/private/url it implies meaning through the fetch_page pipeline reference. A tiny gap: private and max_chars are not individually described, but the framework reference partially compensates.

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 the tool fills forms on a URL and returns the result page as markdown. It explicitly names the resource (form on url), the verb (fill/submit), and distinguishes it from siblings like fetch_page (simple GET) and page_forms (discovery). The examples and the search-box convention make the purpose unmistakable.

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 explicitly tells when to use this tool over alternatives: 'Discover field names first with page_forms(url)', recommends fetch_page for simple GET searches ('lighter'), and enumerates the use cases it unlocks (site search, faceted browsing, GET/POST/JS forms). It also documents the session-riding behavior for logged-in forms.

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