get_similar_ligands_api_compound_similarity__hetcode__get

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

Annotations already declare readOnlyHint=true, so the description's addition of similarity criteria provides some behavioral context. However, it does not disclose potential pagination, rate limits, or error conditions, leaving gaps for a comprehensive understanding.

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 a single, focused sentence that includes all essential information without redundancy. Every clause serves a purpose, making it efficient for an AI agent to parse.

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?

Given the simplicity of the tool (single parameter, no output schema), the description provides the basic functionality but lacks details on the return format or potential limits. This is adequate but leaves room for improvement in completeness.

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 schema covers 100% of the single parameter ( `hetcode` ) with a description. The tool description adds no additional meaning beyond what the schema already provides, resulting in no extra value.

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 returns similar chemical components, specifying the similarity criteria (stereoisomers, common scaffold, ≥60% PARITY). This distinguishes it from sibling tools like get_compound_interaction or get_ligand_summary, making its purpose unambiguous.

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 when finding similar compounds but lacks explicit when-to-use or when-not-to-use guidance. No alternatives or exclusions are mentioned, relying on the agent to infer context from sibling tool names.

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