Compare Proteins Topologically (TDA Fingerprint Distance)

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint and idempotentHint, reducing the burden. The description adds value by explaining the output is a pairwise distance matrix, the metric details, and emphasizing it is not Wasserstein. No contradiction with annotations, and it provides useful behavioral context beyond them.

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?

The description is concise (approx. 150 words), well-structured with purpose, metric details, applications, and caveats. Each sentence adds value, front-loaded with the core action. No redundancy or 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?

Given the tool complexity, presence of output schema, and annotations, the description covers purpose, metric, applications, and limitations thoroughly. It provides sufficient context for an agent to decide when to use it and interpret results, without needing to replicate schema or output details.

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 0% per context, so the description should compensate. It mentions 'provided proteins' but adds no details about uniprot_ids beyond what the schema already states (list of UniProt accessions, 2-10). Without additional format or validation info, it fails to compensate for low schema coverage.

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 explicitly states the tool compares multiple proteins using TDA-fingerprint distance, specifies the distance metric (L2 on 64-dim vectors), and contrasts with Wasserstein distance. It distinguishes from sibling tools like compute_topology_fingerprint by focusing on pairwise comparison. This is specific, with a clear verb and resource.

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?

The description lists applications (drug-repurposing triage, off-target screening, cross-species comparison) and states it is not a functional or sequence-similarity measure, guiding appropriate use. However, it does not explicitly advise against using it for other purposes or compare with specific sibling tools, missing some discrimination.

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