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 usefully adds that results are filtered to UniProt-mapped chains and include UniProt metadata, but says nothing about result volume, pagination, or behavior when a hetcode has no mapped partners.

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; the key scoping qualifier (interacts + mapped to UniProt) appears before the metadata clause. Slightly dense, but every clause earns its place.

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?

For a one-parameter read-only lookup with no output schema, the description adequately covers what is returned (interacting protein chains plus UniProt metadata). Remaining gaps (pagination, empty-result behavior) are minor given the tool's simplicity and its readOnly annotation.

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 carries the parameter burden. The description restates the input as 'the given chemical component' but adds no format, casing, or lookup-syntax detail 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 ('Returns') and a precisely scoped resource: protein chains in PDB entries that interact with a given chemical component AND are mapped to UniProt. That mapping filter distinguishes it from the broader sibling comp_intx_comp_intx_hetcode and ligand_sum_comp_sum, though it names no 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?

Usage is implied: supply a hetcode to get its interacting UniProt-mapped protein chains. There is no explicit when-to-use statement, no exclusions, and no pointer to the sibling comp_intx tool for non-UniProt-mapped interactions, so the agent must infer the boundary.

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