chimerax_screenshot

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

With no annotations, the description fully discloses the behavior: it saves an image, returns the path, specifies the default directory, and notes that a failed view command still allows capture. This adequately covers the operation's side effects and edge cases.

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 well-structured with clear Args and Returns sections, using concise bullet-like text. No unnecessary fluff; all information is actionable.

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 lack of annotations and the presence of an output schema, the description covers the tool's purpose, parameters, return value, and post-capture workflow. It is self-contained and sufficient for an agent to use the tool effectively.

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?

Although the schema provides little to no parameter descriptions, the tool description compensates fully. Each parameter (width, height, format, output_path, auto_fit) is explained with defaults, constraints, and behavior, giving the agent everything needed to invoke correctly.

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 opens with a specific verb+resource: 'Capture a screenshot of the current ChimeraX view.' It clearly conveys the action and scope. However, it does not distinguish this from the sibling chimerax_tool_screenshot, so it misses the top score for sibling differentiation.

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 clear usage guidance, including the instruction to use the Read tool on the returned path and explaining the auto_fit behavior. It does not explicitly discuss when to prefer this over sibling screenshot tools but gives enough context for typical use.

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