chimerax_models

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Get list' implies a read-only operation, the description does not state whether a ChimeraX session must be running, what happens if no models exist, or any error conditions. It adds no behavioral context beyond the basic return value, which is insufficient without annotation support.

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 appropriately brief and front-loaded, stating the core action in the first sentence. The subsequent 'Returns:' line is slightly redundant but not verbose. Every sentence is short and purposeful, though the return statement could have been omitted or expanded with value.

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 tool's simplicity (0 parameters) and the presence of an output schema, the description is largely sufficient. It lacks any mention of session prerequisites or potential failure modes, but for a straightforward list-query tool with an output schema, the core purpose is covered. The absence of usage guidance is the main gap, but it is minor for this tool.

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 tool has zero parameters, so the schema description coverage is trivially 100%. According to the rubric, 0 parameters warrant a baseline of 4. The description adds no parameter-related information, but none is needed given the absence of parameters.

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 tool's action and resource: 'Get list of currently open models in ChimeraX.' It uses a specific verb (Get) and resource (models), which distinguishes it from sibling tools like chimerax_status or chimerax_open. The purpose is unambiguous and immediately understandable.

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 no explicit when-to-use guidance or alternatives. It does not mention when this tool should be preferred over siblings like chimerax_status or chimerax_api_read. There is no exclusion criteria or context beyond the basic action, leaving the agent without direction on selecting this tool among similar ones.

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