chimerax_list_screenshots

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

As a list operation, the behavior is inherently read-only and the description discloses the return contents (path, size, modification time). With no annotations provided, it carries the transparency burden adequately by stating the output details and avoiding any implication of mutation or deletion.

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 short sentences with the main action front-loaded ('List all screenshots...'). Every word earns its place, and the return fields are listed efficiently without redundancy.

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?

This is a simple zero-parameter read-only list with an output schema present. The description states both the scope ('all screenshots saved by chimerax-mcp') and the key return fields, which is fully sufficient for this complexity level.

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 input schema has zero parameters, so the baseline is 4. The description appropriately does not attempt to document parameters that do not exist.

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 explicitly states 'List all screenshots saved by chimerax-mcp', using a specific verb and resource. It is clearly distinct from sibling tools like chimerax_screenshot (capture) and chimerax_cleanup_screenshots (delete).

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 context—listing screenshots saved by this MCP—and implicitly indicates a read-only management operation. It does not explicitly name alternatives or when-not-to-use, but for a simple zero-parameter list, no exclusions are necessary.

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