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

Annotations already declare readOnlyHint and idempotentHint. Description adds details about anti-bot challenges, mode behavior (stealth/fingerprint), signed identity (Web Bot Auth), and colony standing governance for misuse. This provides meaningful context beyond annotations.

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?

Three sentences are efficient and front-loaded with the primary action. However, the second sentence is somewhat dense with details about privileges; could be slightly more structured. Still, it is appropriately concise.

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?

No output schema exists, so description must cover return values. It specifies status, anti-bot challenge, and page as markdown, which is sufficient for most browsing tasks. Does not detail error responses or format of status, but overall 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?

Schema coverage is 100%, but description adds interpretive value: explains that 'stealth' mode enables anti-detection, 'sign=true' assists with compliant authentication, and 'handle' governs privileges. This clarifies parameter semantics beyond the schema definitions.

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 it navigates to a URL and returns status, anti-bot challenge, and markdown content. It distinguishes itself from siblings like browse_read by explicitly mentioning navigation and outputs, but does not explicitly differentiate from browse_navigate or browse_open.

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?

No guidance on when to use this tool versus the many sibling browse tools (e.g., browse_open, browse_navigate, browse_read). The description explains optional parameters and standing implications, but not context for selecting this tool over alternatives.

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