pilot_close

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

No annotations, so description carries full burden. Discloses resource release and error condition 'No browser to close' as safe to ignore. Does not elaborate on irreversibility or impact on other windows, but for a close operation it is adequate.

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?

Description is short, front-loaded with the primary action, and includes use cases, parameter list, return value, and error handling. Every sentence is useful and none are redundant.

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?

For a simple tool with no parameters, the description covers purpose, usage, return type, and errors. No output schema exists, but the stated return ('Confirmation') is sufficient.

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?

No parameters in schema, description simply states 'Parameters: (none)'. This adds no significant meaning beyond the schema, but for zero-parameter tools a baseline of 3 applies.

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?

Description clearly states 'Close the browser instance and release all associated resources.' The verb 'close' and resource 'browser instance' are specific. It distinguishes itself from sibling pilot_tab_close by referring to the entire browser.

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?

Explicitly states when to use: 'when the user wants to end the browsing session, clean up after completing a task, or start fresh with a new browser session.' Does not mention alternatives, but context implies not for tab-level closing.

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