Confirm login & close the window

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

No annotations provided. Description covers main behavior (verify, close, return to headless) and parameter effect. Lacks details on what happens on failure (e.g., not signed in) or side effects.

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?

Two sentences: first states primary action with sibling link, second explains optional parameter. No fluff, perfectly front-loaded.

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?

Simple tool with 1 param and no output schema. Description covers purpose, usage context, and parameter. Could mention error handling or prerequisites, but adequate for the complexity.

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?

Only one parameter (keepHeaded) with schema coverage 100%. Description essentially repeats schema's description. Adds minimal new meaning beyond structured data.

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 action: verifies sign-in after using login, closes window, returns to headless. It explicitly names the sibling tool 'login', distinguishing purpose.

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?

Specifies 'after using the login tool', giving clear usage context. Also explains parameter option (keepHeaded=true). Does not explicitly exclude other scenarios but the context is strong.

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