web_automation_query

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'process natural language queries' and gives examples but does not mention side effects, state changes, return values, or any limitations. For a tool that can clear conversations, this is a significant transparency gap.

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, with the first sentence front-loading the purpose and the second providing three illustrative examples. Every sentence earns its place with no redundant wording.

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?

The tool is simple (one parameter, no nested objects), but the description does not explain what the tool returns or whether it requires prior browser initialization (evident from sibling initialize_browser). This leaves functional gaps that the examples do not cover.

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 already provides a 100% covered description for the sole parameter, and the tool description adds value by giving concrete examples of valid queries, illustrating the variety of natural language commands the tool accepts. This goes beyond the basic schema definition.

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 uses the specific verb 'process' and clearly names target resources (ChatGPT, Gemini, Cloud Desktop), making the tool's function unambiguous. Examples further differentiate it from sibling tools like send_to_service and clear_conversation, which handle specific operations while this is the general NL interface.

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 natural language commands with examples, but it never explicitly states when to use this tool versus the sibling tools (e.g., send_to_service, clear_conversation). It lacks direct guidance on alternative selection.

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