chemdraw_create_document

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

Annotations declare readOnlyHint false, openWorldHint false, destructiveHint false, so no contradiction. However, the description does not disclose what happens on invalid CDXML, whether existing documents are overwritten, what output/return is provided, or any side effects beyond creating a document. For a creation tool with no output schema, this is a significant transparency 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?

Two sentences with no filler. Every clause earns its place: the action, the input format, the output type, and the critical constraint about no name resolver or chemistry invention.

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 one-parameter tool with no output schema and no annotations beyond default flags, the description should cover what happens after creation, error behavior, and any prerequisites. It says the caller supplies validated structures but not what the tool returns or how the agent will know it succeeded. The tool name and siblings suggest a document-management workflow, but the description leaves the success/return semantics implicit.

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 coverage is 0% and there is only one required parameter, cdxml. The description identifies cdxml as the input format (CDXML) and says it must be validated chemical structures, which adds some meaning beyond the bare parameter name. However, it does not specify format details, size limits, or accepted variations.

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?

States a specific verb (create) and object (editable native document from CDXML) and a key constraint (caller supplies validated structures; no name resolver or chemistry invention). It is clear what the tool does, though it does not explicitly contrast with siblings by name.

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 implicitly tells the agent when to use it: when the caller already has validated CDXML and wants an editable native document, and explicitly tells when not to use it (when name resolution or chemistry invention is needed). It lacks an explicit mention of alternatives but the constraint serves as a usage guide.

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