Get Protein Sequence

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

Description adds valuable context beyond annotations: explains that compact mode returns a preview to limit payload, details the effect of canonical_only, and confirms read-only behavior. No contradiction with annotations (readOnlyHint, idempotentHint).

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?

Single paragraph with clear, information-dense sentences. Front-loaded with main purpose. Could benefit from minor structural improvements like bullet points but is sufficiently concise.

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 annotations, output schema, and schema coverage, the description adequately covers input behavior, response_mode variations, and canonical_only. No missing elements for effective use.

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 covers all 3 parameters (100% coverage), and description enriches with examples (e.g., P05067-2 for isoform) and usage tips (e.g., 'cheap for large proteins' for compact mode). Exceeds 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 it returns amino-acid sequences for an entry, specifying canonical and additional isoforms. Distinguishes from sibling tools like get_protein, get_protein_features, etc., which focus on other aspects.

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?

Provides explicit guidance on when to use canonical vs. isoform accessions and how response_mode affects output (e.g., compact mode for large proteins). Lacks explicit comparison to alternative tools but context is strong.

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