ebi-pdbe-comp_intx_proteins_comp_unip_hetcode_b6c68ca3

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. The description adds genuinely new behavioral context: only UniProt-mapped chains are returned and the output carries associated UniProt metadata. It says nothing about result cardinality, ordering, or what happens with an unknown hetcode, and idempotentHint=false is left unexplained.

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 no filler. It is dense but every clause (interaction, PDB entries, UniProt mapping, UniProt metadata) carries distinct meaning.

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 must carry more of the return-value burden, and it does partially by stating that UniProt metadata is included. However, it omits the shape of the response, whether multiple chains/entries per component are returned, and any pagination or empty-result behavior, which matters for a lookup tool keyed on one identifier.

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 100% for the single hetcode parameter, so the schema already documents it (albeit redundantly). The description adds modest meaning by framing hetcode as a chemical component identifier whose interacting partners are looked up; no format examples or validation rules are given.

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 names a specific verb ('Returns') and a precise resource: protein chains in PDB entries that interact with a given chemical component, restricted to those mapped to UniProt. That scope restriction is distinctive enough to separate it from the rather generically named sibling comp_intx_comp_intx_hetcode, though the sibling is never named 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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is referenced. An agent must infer from the phrase 'mapped to UniProt' that results exclude non-UniProt-mapped chains, and must guess how this differs from the sibling comp_intx tool that also takes a hetcode.

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