create_screenshot

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

Annotations already give behavioral hints: not read-only, open-world, not idempotent, not destructive. The description adds no contradictory info and provides useful detail on waitTime behavior. No major gaps.

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?

Concise and front-loaded: first sentence states purpose, then lists parameters with constraints in a bullet-like format. Every sentence adds value, no fluff.

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?

Adequate for a simple capture tool with no output schema. Explains parameters and waitTime use case. Lacks description of output format (e.g., image type) or error cases, but given low complexity, it's minimally sufficient.

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?

Input schema has 100% description coverage, so the schema already explains parameters. The description adds marginal value by explicitly restating constraints and explaining waitTime's use case, but doesn't add deeper semantics beyond what's in 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?

Clearly states it captures a screenshot using RenderForm. The verb 'capture' and resource 'screenshot' are specific. Sibling tools include 'render_image' which could be confused, but the description distinguishes by naming the service RenderForm.

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 context for when to use 'waitTime' (pages with animations or async content). However, lacks explicit guidance on when not to use this tool or alternatives like 'render_image'.

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