Protein Family Analysis

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds context by specifying that data comes from 'curated UniProt annotations' and that output includes 'direct Pfam and InterPro links', which informs the agent about the source and format of the results.

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 a single, front-loaded sentence with no redundant information. Every word contributes to understanding the tool's function.

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 provides a general sense of what the tool returns (summaries with links) but lacks details on the structure, pagination, or how the two optional parameters are used together. The example helps but does not fully clarify behavior.

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% (both parameters have descriptions). The description does not add additional meaning beyond the schema; it restates the general purpose without clarifying parameter-specific semantics like how accession and query interact.

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 clearly states the verb 'Summarize', the resource 'protein family and domain context from curated UniProt annotations', and the added value 'with direct Pfam and InterPro links'. It distinguishes from sibling tools like get_protein_info or pathway_analysis by specifying the focus on family/domain context.

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 implies usage for obtaining protein family and domain summaries but does not explicitly state when to use this tool versus alternatives like get_protein_info or network_enrichment. No exclusions or when-not conditions are provided.

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