ebi-pdbe-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 safety is covered, and the description usefully adds what the payload covers (identifiers, descriptors, synonyms, cross-references). It does not disclose response shape, size, or whether the summary is expensive or truncated, which matters for a broad summary endpoint with no output schema.

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 zero preamble, though the long comma-separated enumeration of content categories is somewhat list-heavy. Every clause is content-bearing; nothing is redundant filler.

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, describing the returned categories is the right compensation and is done here. However, for a summary tool with many hetcode-keyed siblings, the absence of any routing guidance or note on response granularity leaves a meaningful gap.

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?

There is exactly one parameter with 100% schema description coverage, so the baseline is 3. The description confirms 'hetcode' identifies the chemical component, but adds no format, casing, or validity detail (e.g., PDB three-letter codes) beyond the 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 states a specific verb and resource: it returns a summary for the chemical component identified by a hetcode, and it enumerates the content categories (structure identifiers, physico-chemical descriptors, synonyms, metadata, functional annotations, cross-references). An agent knows what the tool does, but nothing distinguishes it from close siblings such as comp_intx_comp_intx_hetcode, comp_in_comp_in_hetcode, or similar_ligands_comp_similarity_hetcode, which also key off a hetcode.

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?

There is no when-to-use guidance at all: no statement of what question this answers that the interaction or similarity tools do not, and no exclusions. The agent must infer from the name and sibling list which hetcode-keyed tool to pick.

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