chemdraw_inspect_symbols

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value beyond that by specifying that the tool takes a snapshot (implying non-mutating) and returns a source_token, plus a caveat that a graphical electron dot is not a verified radical state. This adds semantic nuance without contradicting annotations.

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 (two sentences) and front-loaded with the primary action. It avoids fluff and conveys key points efficiently. It could be slightly more structured (e.g., separating the token explanation), but it is appropriately sized for the tool's simplicity.

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?

The description covers the core behavior and a relevant caveat, but it does not explain the purpose of the source_token or how it is used downstream. It also does not clarify how this tool differs from other inspection tools (e.g., chemdraw_inspect_document) or mention any prerequisites. Given the single parameter and read-only annotations, it is adequate but not complete.

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 schema_description_coverage at 0% and only one parameter (document_id), the description does not explain the parameter's format, purpose, or constraints. The name is self-explanatory, but the description provides no additional semantics, failing to compensate for the lack of schema descriptions.

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 a specific action ('Snapshot native atom/bond/symbol IDs and measured label bounds') and a distinct output ('returning a source_token'). It identifies the resource (symbols in a document) and is not a tautology. However, it does not explicitly differentiate from sibling tools like chemdraw_inspect_document or chemdraw_inspect_annotations, so it loses one point.

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 no explicit guidance on when to use this tool versus alternatives. It mentions supported symbol types (circled charges, electron/lone-pair symbols) but does not state conditions or exclusions. There is no mention of when to prefer this over other inspect tools, leaving the agent to infer usage.

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