search_pdb_structures

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

No annotations are provided, so the description must convey behavioral traits. It only says 'Search PDB' without disclosing result format, pagination, rate limits, or whether it returns summaries or full structures. This omission is critical for a search tool.

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 a single concise sentence that front-loads the core functionality (searching protein structures) with key usages (name, gene, UniProt). Every word is purposeful with no redundancy.

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, the description should clarify what the search returns (e.g., PDB IDs, metadata). It lacks this and also omits prerequisites, network requirements, or fallback behavior. The tool's complexity is low, but missing return-value context reduces completeness.

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%, and the description adds no new meaning beyond the schema. The query parameter description already details acceptable IDs, and limit is standard. Description merely rephrases the schema, earning the baseline score.

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 the tool searches PDB for protein 3D structures and specifies acceptable inputs (protein name, gene name, UniProt ID). It distinguishes itself from sibling tools like 'get_pdb_structure' which retrieves by PDB ID, and 'search_alphafold' which searches a different database.

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?

The description implies usage for finding structures from identifiers but offers no explicit guidance on when to use this tool versus alternatives such as 'get_pdb_structure' for known PDB IDs or 'search_alphafold' for AlphaFold models. No when-not-to-use advice is given.

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