simulate_googlebot

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

No annotations exist, so the description fully carries the transparency burden. It discloses key behaviors: authentic user-agent, requestIdleCallback simulation, network interception, and capture of timing/events/screenshots. It doesn't mention limits or error handling, but the transparency is high.

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 concise and well-structured: a one-line summary, a bulleted list of features, and a bulleted list of use cases. Every sentence is informative with no redundancy.

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 three parameters (one nested), no output schema, and no annotations, the description covers the tool's purpose, behavior, and use cases adequately. It mentions return values (timing, events, screenshots) but lacks details on output format. Still, it is complete for the complexity level.

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 description coverage is 100%, so the schema already documents parameters well. The description adds context about the tool's purpose (e.g., capturing analytics events) that complements the eventPattern parameter, but it does not provide new parameter-level details beyond the schema.

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 'Simulate Googlebot crawling a page and capture analytics events.' It provides a specific verb and resource, and lists detailed behaviors and use cases. Without sibling tools, it effectively distinguishes itself.

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 explicitly lists four verification scenarios ('Use this to verify:...'), providing clear usage context. It lacks explicit alternatives or when-not-to-use statements, but the absence of sibling tools reduces the need for exclusion guidance.

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