uniprot_search

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

Discloses that size is capped at 500 server-side, explains response_format values, and clarifies that organism and reviewed_only are shortcuts. Annotations already indicate readOnlyHint and openWorldHint, but this adds valuable operational details.

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, front-loaded with purpose and usage, followed by examples and parameter explanations. Every sentence adds value with no fluff.

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 output schema exists, description needn't explain returns. It covers purpose, usage, parameter semantics, and behavioral traits, and distinguishes from sibling tools, making it fully complete.

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?

With 100% schema coverage, baseline is 3. The description adds significant meaning: examples of query syntax, explanation of organism/reviewed_only as shortcuts, and description of response_format values, exceeding the schema's default descriptions.

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 it's the general-purpose entry point for finding UniProtKB proteins by any combination of gene, organism, keyword, or free text, and distinguishes from sibling uniprot_get_entry by specifying when to use each.

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?

Explicitly says 'Use this first when you don't already have an accession; use uniprot_get_entry once you do.' Also explains that reviewed_only and organism are convenience shortcuts equivalent to adding clauses to query.

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