browser_schedule_snapshot

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

With no annotations, the description must fully disclose behavior. It mentions 'in-memory read-only' but does not explain what happens if the process ends, how to retrieve the snapshot, whether a previous scheduled snapshot is replaced, or any rate limits. The vague phrase about 'exact grant and MCP process' is insufficient.

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 a single sentence, which is concise, but it leaves out essential details. Conciseness is not a virtue when it sacrifices completeness; the sentence does not earn its place because it is too vague to be useful.

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 the tool's complexity (scheduling, 3 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain the snapshot lifecycle, parameter semantics, or how to use the result. The tool is part of a family (snapshot, schedule, status, cancel, result), but the description isolates it without context.

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 0%, yet the description adds no information about the three parameters (collaboration_id, delay_seconds, max_items). It does not clarify their purpose, format, or constraints beyond what parameter names imply. This is a critical gap.

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 identifies the tool as scheduling a snapshot ('schedule one... snapshot'), distinguishing it from the immediate 'browser_snapshot' sibling. However, the phrase 'while the exact grant and MCP process remain live' is unclear and reduces precision.

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 is provided on when to use scheduling versus immediate snapshot, or how this tool relates to sibling tools like browser_schedule_status, browser_schedule_cancel, or browser_schedule_result. The description does not mention prerequisites, alternatives, or exclusions.

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