ligand_sum_comp_sum_hetcode_e2f08774

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 value by enumerating what the summary contains (structure IDs, descriptors, synonyms, PDB metadata, functional annotations, cross-refs). It does not explain the unusual idempotentHint=false for what is clearly a pure read, nor any return format or rate behavior.

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 front-loaded sentence with the core action first and the content enumeration second. The long list of returned categories is slightly padded but every element is informative, with no wasted framing.

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 no output schema, the description usefully enumerates the returned content categories, which is exactly what an agent needs to judge relevance. Given a single well-documented parameter and read-only annotations, this is nearly complete, missing only explicit routing to/from sibling tools.

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?

Only one parameter ('hetcode') with 100% schema description coverage, so the schema carries the parameter documentation. The description reinforces that hetcode identifies the compound but adds no format, case, or lookup semantics beyond that. Baseline 3 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?

States a specific verb ('returns a summary') and resource ('chemical component identified by the given hetcode'), then enumerates the content categories. This differentiates it from interaction siblings like comp_intx and similarity tools like similar_ligands, though it never names a sibling explicitly.

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 when-to-use guidance, no preconditions, and no alternative tools named. The agent must infer from the purpose alone that this is the broad summary entry point versus the more specialized sibling tools.

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