pdb2gmx

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds minimal behavioral context beyond stating the output (topology and coordinates). It does not disclose file creation, overwriting behavior, or required permissions. Given the limited annotation info, the description should provide more detail about side effects.

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 concise sentence, which is efficient, but it lacks structure. It does not separate purpose, inputs, outputs, or usage. It is appropriately short but could benefit from a clearer breakdown.

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 8 parameters with no schema descriptions and a minimal description, the tool is missing critical context. The existence of an output schema is not leveraged in the description. Essential information about parameter meanings, required format, and typical usage is absent, making the description incomplete for effective use.

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 description coverage is 0%—the input schema has no descriptions for any of the 8 parameters. The tool description 'Build topology and processed coordinates from a PDB/GRO structure' adds no parameter-level information. An agent must guess the meaning of parameters like 'ignh', 'water', 'forcefield', etc., which is insufficient.

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 purpose: building topology and processed coordinates from PDB/GRO structures. It uses a specific verb ('build') and identifies the resource (topology and processed coordinates) and input format. However, it does not distinguish this tool from siblings like 'editconf' or 'solvate', so it is not a perfect 5.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, required steps, or when not to use it. Usage is only implied by the general purpose.

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