screenshot

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions optional width/height but does not specify image format, return details, or state that the action is non-destructive. While the tool's behavior is largely obvious from its purpose, the description could be more explicit.

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 two sentences with no wasted words. The first sentence covers purpose, the second adds parameter info. It is efficient but could be slightly more structured (e.g., bullet points or clearer separation of purpose and usage).

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 2 optional parameters and no output schema or annotations, the description covers the basic purpose and parameter optionality. However, it lacks details on return format, real-time behavior, or edge cases, which would be helpful for an agent.

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%, so the description must compensate. It states 'Optionally specify width/height', which clarifies that parameters are optional and control dimensions, but it does not provide units, default values, or range constraints. This adds minimal meaning beyond the schema's property names.

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 verb 'capture', the resource 'current 3D preview', and the purpose 'so you can visually inspect the model and iterate'. It distinguishes from sibling 'screenshot_views' by specifying the current 3D preview.

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 visual inspection but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives like screenshot_views. It is adequate but lacks clear context.

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