chemdraw_doctor

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 the useful behavioral detail that it checks 'Mac installation, live connection and optional chemistry validator' and that it does not edit documents. It does not disclose what the output looks like or what 'optional' means in practice, but for a zero-parameter diagnostic tool the added context is adequate.

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 that front-loads the action ('Check'), names the three checked areas, and explicitly excludes document editing. Every word earns its place; there is no fluff or repetition of the tool name.

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 diagnostic tool with no output schema, the description is largely complete: it states what is checked and what is not done. The only minor gap is not describing the return format or how the 'optional chemistry validator' is triggered, but given the tool's simplicity and annotation coverage, this is a small omission.

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 there is no parameter semantics burden on the description. The description still clarifies the tool's scope (installation, connection, validator) which is the only meaningful semantic content an agent needs. Baseline 4 for zero-parameter tools is appropriate.

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 states a specific verb ('Check') and resource ('Mac installation, live connection and optional chemistry validator') and explicitly notes it does not edit documents. It is clear enough to distinguish from the many sibling tools that perform document edits or build operations, though it does not name a specific sibling alternative.

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 this is a diagnostic/health-check tool to run before other operations, and the 'without editing documents' phrase signals it is safe to use in read-only contexts. However, it does not explicitly state when to use it versus alternatives or when not to use it, leaving the agent to infer its role from the sibling names.

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