recognize_structure_image

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

No annotations provided, so description must disclose all behavioral traits. It mentions 'register candidate SMILES' implying a side effect (registration) but does not explain if the endpoint modifies data, what happens on failure, or if there are rate limits. The word 'candidate' hints at verification but no further detail.

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?

Single concise sentence with no redundant information. Every word is necessary to convey the action.

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?

With 0% schema coverage, no annotations, and an output schema (unseen), the description should provide more context. Missing: explanation of output, error handling, configuration of endpoint, and relationship to other tools. It is too sparse for effective use.

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%, so description must explain parameters. It does not describe any parameter: image_path format, purpose of reaction_step_id (association with reaction step?), token (authentication?). The description adds no meaning beyond the raw schema.

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 action: sending an image region to an optical structure recognition endpoint and registering candidate SMILES. The verb 'send' and nouns 'image region', 'endpoint', 'register candidate SMILES' provide specific purpose. This distinguishes it from sibling tools like search_by_smiles or search_compounds.

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?

No guidance on when to use this tool versus alternatives. No mention of prerequisites, context such as needing a configured endpoint, or when not to use it (e.g., for full images, not regions). The description assumes the agent already knows when to invoke this tool.

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