search_uniprot

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

Partially describes output (returns function, sequence, associated genes) but does not disclose side effects, permissions, or limitations. No annotations exist, so description carries full burden and falls short of full transparency.

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?

Two sentences, zero superfluous words. Front-loaded with core action and result. Highly efficient.

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 no output schema and full schema coverage, the description adequately covers purpose, query types, and output. Could mention default organism and limit but schema compensates.

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 coverage is 100%, so baseline is 3. The description does not add meaningful parameter information beyond what the schema already provides; it merely restates query options.

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?

Clearly states the verb 'Search', the resource 'UniProt for protein information', and specifies valid query types (protein name, gene name, UniProt ID). Distinguishes from sibling search tools like search_ncbi_gene by focusing on UniProt and protein information.

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?

Implies usage context (need protein information) but does not explicitly state when to avoid this tool or suggest alternatives like get_protein_details. Lacks precise usage boundaries.

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