uniprot_get_sequence

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

Discloses that output is always markdown/plain-text FASTA and that there is no response_format parameter. Consistent with readOnlyHint and openWorldHint annotations.

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 that front-load the core action, then provide usage guidance and a relevant detail about the output format. No superfluous text.

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?

Covers purpose, usage context, output format, and parameter behavior. With an output schema present, explanation of return values is unnecessary.

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?

The only parameter (accession) is well-described in the input schema. The description adds value by clarifying the absence of other parameters (no response_format), so it goes beyond baseline 3.

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 'Fetch the canonical protein sequence in FASTA format', specifying the verb, resource, and output format. Distinguishes from sibling uniprot_compute_properties by contrasting use cases.

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 when you need the raw residue string itself' and advises calling uniprot_compute_properties for derived properties, providing clear differentiation among siblings.

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