search_proteins

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

Annotations already provide readOnlyHint and idempotentHint, and the description adds behavioral details: case-insensitive prefix matching and the result contents (HGNC id and description). There is no contradiction, and the description adds context beyond annotations, though it doesn't discuss pagination or limit behavior.

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 concise sentences, front-loaded with the core action and followed by result and usage advice. No redundant information.

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?

The description covers the search semantics, result fields, and recommended workflow. It does not explicitly describe the limit behavior or potential empty results, but these are minor for a search tool. Given no output schema, the return description is adequate.

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 schema has 0% description coverage, so the description must explain the parameters. It implicitly explains q as a symbol prefix but does not explain the limit parameter or its effect. This is a partial contribution, but not fully compensating for the schema gap.

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 states a specific verb ('Search'), a specific resource ('proteins'), the method ('by symbol prefix'), and case-insensitivity. It also mentions what it returns (HGNC id and description) and distinguishes it from the sibling get_protein by explicitly saying to use this first and then call get_protein.

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 instructs the agent to use this tool first to resolve a protein of interest, then call get_protein. This provides a clear when-to-use scenario and names the alternative tool, fulfilling the usage guideline criteria.

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