analyze_solution

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

No annotations are provided, so the description bears the transparency burden. It discloses what the tool returns (R1, alpha, space group, Flack x, atom count), which is helpful, but doesn't describe edge cases such as expected behavior if inputs are empty/null or malformed, or how multiple solutions are handled.

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 reasonably concise with three short paragraphs, front-loading the purpose. The second paragraph adds meaningful param context. Slightly verbose in naming file extensions but no wasted sentences.

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 two optional params, no annotations, and an output schema that presumably defines return fields, the description adequately explains what data to pass and what will be returned. It could be more explicit about null-handling and scenario guidance for partial inputs, but is complete for the core use case.

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?

Schema coverage is 0%, so the description must carry the param documentation burden. It does explain that 'lxt' is the listing text and 'res' is a solution model, and that both are optional-ish ('Pass the listing text as lxt and a solution model as res'). However, it doesn't clarify what happens if only one is provided or the expected format/text constraints of each.

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 verb ('Summarise'), the resource ('a SHELXT structure-solution run'), and the specific inputs/outputs. It distinguishes from the sibling analyze_results by specifying it targets SHELXT output files (.lxt/.res).

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 gives clear context on when to use it (after a SHELXT run) and what inputs to pass (.lxt and .res text). It doesn't explicitly state when NOT to use it or name alternatives like analyze_results, which slightly limits the score.

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