charlotte_submit

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

No annotations are provided, so the description carries full burden. It only states 'Returns full page representation after submission' but does not disclose potential side effects, error conditions, or required permissions. For a form submission tool, more behavioral context is needed.

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 long, front-loaded with the main action, and contains no unnecessary words. Every sentence adds value.

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 the tool's simplicity (1 parameter, no output schema, no annotations), the description covers the basic function and return type. However, the misleading mention of a click method without corresponding parameter and lack of error handling or prerequisites make it minimally adequate.

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 schema provides 100% coverage with a description for form_id ('Form ID from page representation'). The description adds mention of an alternative 'clicking' method but doesn't clarify how that maps to the parameter, creating inconsistency. Baseline is 3 due to high schema coverage, and the description adds little 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 'Submit a form' and specifies two methods (by form ID or clicking submit button), which distinguishes it from sibling tools like charlotte_click, charlotte_type, etc. It also mentions the return value, providing full context.

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 two submission methods but only one parameter (form_id) is provided, creating confusion about how to perform the 'click submit button' method. No guidance on when to use this tool vs charlotte_click or other alternatives, and no exclusion criteria.

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