ui-screenshot

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action and condition, but fails to mention what happens if the API is unavailable, potential side effects, required permissions, or error handling. For a screenshot tool, this is minimal.

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 a single, concise sentence with no extra words. It is front-loaded with the action and condition, making it highly efficient.

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 two parameters and no output schema, the description provides only the basic action and a condition. It lacks usage guidance, behavioral details, and differentiation from similar screenshot tools, making it incomplete for an agent to decide when to use it correctly.

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?

The description does not mention any parameters. Although the input schema provides titles for both parameters (full and path), the schema description coverage is 0%, and the description adds no additional meaning beyond what the titles already imply. It does not compensate for the lack of descriptions.

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 it captures Blender's UI screenshot with a specific condition (when screen.screenshot is available). The verb and resource are specific, but it doesn't explicitly distinguish from similar tools like feedback-capture or ui-redraw.

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 provides a usage condition ('when screen.screenshot is available'), giving some context. However, it doesn't mention when to use this tool over alternatives or any exclusions, leaving the agent to infer the appropriate context.

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