get_uniprot_generic_unipdb_api_uniprot_unipdb__uniprot_acces

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

Annotations declare readOnlyHint=true, and the description reinforces read-only behavior. It adds value by detailing the extensive response content (sequence, chains, residues, etc.), which is beyond the annotation's scope.

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 verbose, listing many response details in a single paragraph. It could be more concise by grouping related items or removing redundant phrases like 'This endpoint provides...'.

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?

Without an output schema, the description compensates by enumerating many response fields (sequence, mutations, resolution, etc.). It provides a solid overview, though it uses 'such as' indicating it's not exhaustive.

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 description coverage is 100%, so the parameter is documented. The tool description restates the parameter's role but does not add new semantic detail beyond the schema. Baseline 3 is appropriate.

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 specifies the verb 'Retrieve' and the resource 'comprehensive information on PDB structures mapped to a given UniProt accession.' It distinguishes this tool from siblings like get_uniprot_generic_interface_residues by being the generic endpoint for all mapped PDB structures.

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 when comprehensive PDB structure info for a UniProt accession is needed, but it lacks explicit guidance on when to use this tool vs. alternatives. No when-not-to-use or alternative references are provided.

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