camofox_scroll_element_and_snapshot

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

No annotations provided, so description carries all burden. It discloses composite action (scroll + snapshot), return values (scroll position and snapshot), and the waitMs parameter implies a wait before snapshot. Missing details like side effects or auth needs, but for a straightforward combination tool this is adequate.

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?

Extremely concise: two sentences with no wasted words. First sentence states the action; second sentence provides context and return values. Information is front-loaded and scannable.

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?

Covers purpose, usage context, and return values. Does not explain the roles of selector and ref parameters (but schema does). With no output schema, the description compensates by mentioning returns. Overall sufficiently complete for the tool's complexity.

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% (every parameter has a description). Description adds no additional semantics beyond what the schema already provides for each parameter. Baseline score 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?

Description clearly states the action: scroll a container and take a snapshot. It explicitly combines two sub-tools (scroll_element and snapshot), distinguishing from sibling tools like camofox_scroll_element (only scroll) and snapshot (only snapshot). The use case (lazy content in modals) adds specificity.

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?

Provides a concrete example ('incrementally loading lazy content in modals e.g. Facebook group post comments'), suggesting when to use. Does not explicitly exclude alternatives (e.g., using separate tools) but the context of sibling tools and the description's 'combines' hint at the trade-off.

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