chemdraw_import_style

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

The description aligns with annotations (readOnlyHint=true, destructiveHint=false) by stating it does not open ChemDraw or modify the source. It adds behavioral details beyond annotations, such as returning validated preset settings, a hash, defaults used, and unapplied properties, and notes that custom fonts are checked on the rendering Mac. This enriches the agent's understanding of side effects and dependencies, though it could have disclosed more about error handling or output format.

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 concise, with three sentences that front-load the primary purpose, then add usage guidance and limitations. Every sentence provides value—no filler or redundancy. It is well-structured for quick parsing by an agent.

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 simple read-only tool with one parameter and no output schema, the description is fairly complete. It specifies the input type, what it returns (validated settings, hash, defaults, unapplied properties), and how to use the result. It also mentions limitations. Minor gaps include lack of error behavior and exact return structure, but these are not critical for a straightforward operation.

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?

With a single parameter 'path' and 0% schema description coverage, the description must clarify the parameter's meaning. It implicitly conveys that 'path' points to a local .cds/.cdx/.cdxml file by stating the tool reads such files, which adds some context. However, it does not explicitly describe the parameter, its format, or any constraints (e.g., absolute vs. relative path), leaving room for interpretation. The description partially compensates for the lack of schema coverage but not fully.

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 function: reading a local .cds/.cdx/.cdxml document style without modifying it. It explicitly names the resource type and the non-destructive nature, and the mention of returning preset settings to be passed to draw/polish/grid/apply_style distinguishes it from sibling tools like chemdraw_import_file or chemdraw_create_lab_style.

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 clear usage context by instructing to pass the returned preset object to draw/polish/grid/apply_style, indicating when to use this tool. It also states limitations (only typography and bond settings, not template artwork, page geometry, or colour palette), which guides appropriate usage. However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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