comet_screenshot

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

With no annotations, the description carries the behavioral burden. It clearly discloses the return format (base64 PNG) and the effect of the full_page flag, which is the key behavioral toggle. It omits minor details like image dimensions or load-wait behavior, but the core behavior is transparent.

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 crisp sentences with an args section. The core action and return type are front-loaded, and every sentence earns its place without extraneous detail.

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?

For a simple tool with one optional parameter and a stated return format, the description is fully sufficient to invoke it correctly. It covers the only toggle, the target ('current Comet page'), and what the caller receives.

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?

Although the schema's property has no description, the tool description manually documents full_page as 'Whether to capture the full scrollable page.' This adds the exact meaning an agent needs beyond the schema's title and default value.

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?

States a specific verb and resource: take a screenshot of the current Comet page. The return format (base64 PNG) further clarifies the tool's role and distinguishes it from siblings like comet_read_page, which would read page content.

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?

Usage is implied by the action itself: use this when a visual capture of the current page is needed. However, it does not explicitly contrast with alternatives such as comet_read_page or state when not to use the tool.

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