chemdraw_list_documents

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 fully covered and the description does not need to repeat it. The description adds the 'running' scope and the returned fields, which is useful context beyond the annotations, but it does not mention edge behavior such as empty result sets or exact return formatting. This is adequate given the annotations, but not rich.

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?

A single sentence with the verb and resource front-loaded, followed by a tight list of returned fields. Every word earns its place, and there is no repetition of structured data or filler.

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 with no output schema, the description states both the scope ('running' documents) and the return content (IDs, names, paths, modified flags). Combined with the readOnly and destructive annotations, an agent has enough information to invoke the tool and interpret its result correctly.

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 and an empty schema, so there is no parameter burden for the description to carry. Per the rubric, a zero-parameter tool earns a baseline of 4; no additional parameter explanation is needed.

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 uses the specific verb 'List' with the resource 'running ChemDraw documents' and enumerates exactly what is returned: unique IDs, names, paths and modified flags. This clearly distinguishes it from sibling tools such as chemdraw_list_styles and chemdraw_inspect_document, so an agent can identify its purpose without inspecting schemas.

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 usage: call this when you need to enumerate currently running ChemDraw documents and their IDs. However, it provides no explicit when/when-not guidance and names no alternatives, even though siblings like chemdraw_inspect_document, chemdraw_close_working_document, and chemdraw_create_document offer related document operations. The usage context is inferred rather than stated.

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