ebi-pdbe-unip_var_unip_var_unip_acc_6a476541

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 and the description does not contradict it. The description does add useful behavioral context about what comes back (sequences, variant features, PolyPhen/SIFT predictions, cross-references), which matters because there is no output schema. It says nothing about pagination, rate limits, error behavior for unknown accessions, or why idempotentHint is false on a read operation.

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?

Purpose is front-loaded in the first clause, followed by return-value detail, which is the right ordering for a fetch tool. The closing phrase 'enabling comprehensive analysis of protein sequence variations' is pure filler and the return enumeration is long, but overall the text stays on topic.

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 the return-value burden and it does so thoroughly, listing sequence, identifiers, variant features, clinical significance, and predictions. The remaining gap is operational guidance (routing vs siblings, behavior for invalid accessions) rather than missing output information.

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 required parameter, so the schema already explains the input and the description adds little beyond it. It implies the accession must be a UniProt (not PDB) identifier, which is mildly useful disambiguation, but adds no format or validation detail.

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 opens with a specific verb+resource: 'Retrieve variation details for a given UniProt accession.' That is unambiguous about what is fetched and the keying identifier. It does not, however, distinguish itself from structure-side siblings such as ebi-pdbe-var_ent_var_id_entity_id, which is also variation-related but keyed by PDB entity, so an agent must infer the difference from the parameter name alone.

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 explicit when-to-use guidance, no prerequisites, and no named alternative. The description never says to prefer this tool over the PDB-entity variation sibling or over the other UniProt-keyed tools like unip_giruiru or unip_gen_annot, leaving routing entirely to inference from the accession parameter.

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