chimerax_api_read

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

No annotations are provided, so the description must disclose behavioral traits. It says 'bounded' but does not explain the bound, error handling, or return format. Even though 'read' implies a safe operation, it does not confirm whether the tool is read-only or describe what happens with invalid targets.

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 sentence with no wasted words, front-loading the verb and resource. It is appropriately concise, though it could benefit from a brief clause about parameter usage without becoming verbose.

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?

Despite having only 2 parameters and an output schema, the description leaves critical gaps: it does not clarify what 'target' should be, what 'bounded' means, or what the output contains. It is insufficient for an agent to correctly select and invoke this tool without additional information.

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 schema has 0% description coverage, and the tool description does not explain the meaning of 'target' or 'max_chars'. While 'max_chars' is somewhat inferable, 'target' is ambiguous—it could be a file path, symbol name, or query. The description fails to compensate for the lack of schema documentation.

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 uses a specific verb ('Read') and identifies the resource as 'bounded static ChimeraX API documentation content', making the core purpose clear. It does not explicitly differentiate from sibling tools like chimerax_api_search, but the name and wording imply a distinction between reading content and searching it.

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?

No guidance is provided on when to use this tool versus alternatives such as chimerax_api_search or chimerax_guide. The description lacks any context about prerequisites, typical use cases, or situations where another tool would be more appropriate.

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