Get Form

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

With no annotations, the description carries full burden. It discloses key behaviors: returns XML with per-field eids, state, constraints, and suggested next field. It also explains the effect of the 'include_values' parameter and that sensitive values are masked. However, it does not mention error handling or performance characteristics, so a perfect score is not warranted.

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 two sentences with zero waste. The first sentence states the core function, and the second provides usage guidance and output summary. Information is front-loaded, and every sentence earns its place.

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?

Despite no output schema, the description explains the return format (XML with fields). All three parameters are well-documented in both schema and description. Given the tool's complexity and the sibling context, the description provides complete guidance for an agent to use it effectively.

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 100%, and the description adds significant value beyond the schema. For 'form_id' it clarifies 'from a prior get_form call'; for 'page_id' it explains default behavior; for 'include_values' it notes default and sensitive value masking. This extra context helps the agent use parameters correctly.

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's purpose: 'Analyze all forms on the page: fields, required inputs, validation rules, and field dependencies.' It uses a specific verb ('Analyze') and resource ('forms on the page'), and distinguishes itself from sibling tools like 'get_element' or 'get_field' by being form-specific and returning structural information.

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?

Explicit guidance is provided: 'Call this first on any multi-field or multi-step form to plan the fill order, instead of scrolling and screenshotting.' This tells the agent when to use the tool and offers an alternative approach, making it easy to decide.

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