chemdraw_list_styles

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the tool returns numeric style presets and clarifies that it doesn't cover chemistry or layout engines, which is extra context beyond the annotations. It doesn't describe return format, but for a list tool with no output schema, that's a minor gap.

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 extremely concise—one sentence with no fluff. It front-loads the core purpose ('List numeric style presets') and adds qualifying context in the second clause. Every word earns its place, and it's perfectly sized for a simple list operation.

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, read-only list tool, the description covers the essentials: what it lists, the scope (defaults and overrides), and what it excludes. Given the annotations cover safety and the schema is empty, it's complete enough for an agent to know when to call it and what to expect. Missing explicit output format is a minor gap.

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 zero parameters, so the input schema is trivially complete. The description doesn't need to add parameter meaning, and it provides sufficient context about what the list contains. Baseline 4 is appropriate for a no-parameter tool.

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 it lists numeric style presets, distinguishing itself from related style operations like create_lab_style or apply_style. It specifies the scope (defaults plus explicit text/bond overrides) and clarifies what it is not (chemistry or layout engines), which differentiates it from sibling tools.

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 when to use this tool: when you need to list available numeric style presets. It doesn't explicitly state when not to use it or name alternatives, but the distinction from chemistry/automatic layout engines suggests what this tool is not for. With 36 siblings, more explicit exclusions would help, but the context is reasonably clear.

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