SnapForge screenshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, making the read-only nature clear. The description adds only that full-page is the default, which is a minor behavioral detail. There is no contradiction, but the description does not significantly enhance transparency beyond the 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?

The description is extremely concise, consisting of two short sentences that front-load the core purpose. Every word serves a purpose, with no redundancy or filler. It is well-structured for quick parsing by an AI agent.

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 has 10 parameters and a complex input schema, the description is too sparse. It only highlights the full-page default, ignoring other important configurable options like delay, scale, width, height, and waitUntil. While the output schema may document return values, the description fails to guide the agent on how to effectively use the tool's capabilities.

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 every parameter already has a description in the input schema. The tool description does not add any additional meaning or usage context for parameters like delay, scale, or waitUntil. Thus, it meets the baseline but adds no extra semantic 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?

The description clearly states the action ('Capture a screenshot'), the resource ('public URL or raw HTML'), and the output format ('image (PNG/JPEG)'). It also mentions 'Full-page by default,' which adds specificity. This distinguishes it from sibling tools snapforge_pdf and snapforge_markdown, which handle different output types.

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 implies usage for capturing visual representations of web content, but it does not explicitly state when to use this tool versus alternatives like snapforge_pdf or snapforge_markdown. No 'when-not' or exclusion criteria are provided, leaving the agent to infer context from the tool name and siblings.

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