list_commands

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

Describes output differences with/without filter: without filter returns one-line descriptions, with filter returns full detail (regex, params). No annotations, so description must stand alone; it adequately discloses behavior.

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?

Three concise sentences: purpose, behavior clarification, and examples. No redundant information, well-organized.

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?

Complete for a documentation tool with one optional parameter. Output schema exists for return details. Covers what tool does, parameter usage, and use case. No missing critical 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?

Schema only provides name and default; description adds that filter is a substring match against names and descriptions, and its presence triggers detailed output. Fully clarifies parameter meaning and effect.

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?

Clearly states it lists PyMOL commands accepted by parse_and_execute, with distinct behaviors for with/without filter. Distinguishes from sibling tools list_instances and parse_and_execute.

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?

Explicitly explains when to use filter (for full detail on matches) vs without (list all). Suggests use case: 'confirm syntax before calling parse_and_execute'. Lacks explicit when-not-to-use alternatives.

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