query_ff_presets

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

With no annotations provided, the description must disclose behavior. It clearly states the return type ('dict mapping preset name → description string'), which is the primary observable behavior. It does not mention side effects or read-only status, but for a listing tool this is minimal and acceptable.

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 compact and well-structured: a one-sentence summary, a clear 'WHEN TO USE' section, and a 'Returns' line. Every sentence adds value, and the most important information is front-loaded.

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 zero parameters, a declared output schema, and a simple return format, the description is complete. It even includes usage context and a return type description, leaving no critical gaps for the agent to navigate this tool correctly.

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?

There are no parameters, so the schema fully covers parameter semantics. The baseline for zero parameters is 4, and the description appropriately does not attempt to add parameter details that don't exist.

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 ('List') and resource ('force-field presets for relax_pdb_structure'), clearly distinguishing it from sibling tools like split_pdb or fix_pdb_structure. It states exactly what the tool does without ambiguity.

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 'WHEN TO USE' section explicitly instructs to call this tool before relax_pdb_structure when unsure about presets or wanting to present options. This provides clear contextual guidance and names the relevant sibling tool, fulfilling the 'when and alternatives' criterion.

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