chemdraw_apply_style

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

Annotations only declare readOnlyHint=false and destructiveHint=false, which are minimal. The description adds meaningful behavioral context: it creates a copy (so the original is presumably untouched), it does not normalize coordinates or reposition charges, and cleanup is separate. These are important side-effects and limitations beyond what annotations convey, though it does not address return values or side effects like saving or versioning.

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: three short sentences, with the primary purpose front-loaded. It adds only necessary exclusions (coordinates, charges, cleanup) without fluff. Every sentence earns its place, and the structure is clear and scannable.

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 mutating tool with no output schema and no parameter descriptions, the description is incomplete. It lacks any explanation of what 'preset' options exist, what document_id refers to, or what the tool returns (e.g., the new copy's ID). While it covers the operation's scope, it leaves crucial invocation details undefined, especially given the flexible preset parameter.

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%, meaning the schema has no parameter descriptions. The description mentions neither 'document_id' nor 'preset', and does not hint at what 'preset' accepts (enum or object). With two parameters and one being complex (enum/object), the description fails to provide any semantic help. This is a severe gap.

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: 'Create a styled copy with consistent explicit fonts/strokes.' It identifies the resource (a copy) and the action (applying style), and distinguishes itself by noting what it does NOT do (normalize coordinates, reposition charges, or clean up). This differentiates it from sibling tools like chemdraw_clean or chemdraw_apply_route, though it could be more explicit about the 'styled copy' concept.

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 gives implicit usage guidance: it mentions 'Cleanup is a separate explicit action,' implying you should not expect cleanup here, and that coordinates/charges are not normalized, suggesting other tools handle those. However, it does not explicitly name alternative tools or state when to choose this over siblings. The guidance is contextual but not explicit enough to be a 4.

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