shelx_info

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

No annotations are provided, so the description carries the full burden of disclosure. The description clearly signals this is a read-only informational query (reports configuration), which is useful. However, it doesn't describe the output format or what happens if no SHELX directory is configured, which could be relevant behavioral context.

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?

One sentence that conveys the tool's complete purpose with zero waste. It efficiently covers what the tool does (reports information) and what it reports (directory and available programs). No filler or 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?

For a zero-parameter informational tool with an output schema, the description is reasonably complete. It tells the agent what information will be provided. It could mention what might cause the report to differ (e.g., uninstalled/unconfigured SHELX), but for such a simple tool, the description covers the essential purpose adequately.

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 0 parameters, and the schema shows no properties. With no parameters to document, baseline is 4. The description appropriately focuses on the tool's function rather than parameter semantics since there are none.

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 states the tool reports the configured SHELX directory and available programs. This is a specific verb+resource ('report which directory') that clearly distinguishes it from siblings like run_shelx, solve, and refine, which perform actions rather than information queries. The purpose is clear and specific.

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 implies this is an informational tool to be used before running SHELX programs, but it doesn't explicitly say when to use it versus alternatives like list_commands or command_help. The context of being an info/reporting tool distinguishes it from action tools, but there's no explicit when/when-not guidance.

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