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

The annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, so the agent knows this is a side-effectful, open-world operation. The description adds valuable context: 'The real Chrome browser may navigate, fill forms, and submit data on third-party websites as the task requires.' This goes beyond the annotations by specifying actual behaviors, which helps the agent anticipate side effects. No contradiction.

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, front-loaded with the core purpose, followed by a contextual note about browser behavior. Every word earns its place; there is no redundancy or filler.

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 that the schema covers all parameters and an output schema exists to define return values, the description provides the essential context: the purpose and the real-browser behavior that may have side effects. It could mention prerequisites like needing a valid session ID from create_session, but that is implied and captured in the schema. The description is sufficiently complete for an agent to understand what the tool does and what to expect, though it could briefly mention state changes or error conditions.

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 input schema provides 100% coverage for all 12 parameters, each with descriptive text. The description itself does not add any additional meaning to the parameters beyond what the schema already states. Since the schema covers everything, the baseline of 3 is appropriate.

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 sends a new task to an existing browser session, tying it to create_session. It specifies the verb 'send' and the resource 'task'. However, it does not explicitly differentiate from potentially similar tools like browser_task or create_workflow, relying on the context of 'existing session' to distinguish. This is clear but could be more explicit about its unique role among siblings.

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 gives clear context: use for existing sessions created via create_session. This implies a workflow where create_session precedes this tool. However, it does not provide any exclusions or mention when to use alternative tools, such as browser_task for direct browsing or create_workflow for multi-step tasks. The context is clear but not comprehensive.

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