get_sequence_conservation_pdb_entity_api_pdb_sequence_conser

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

Annotations already mark the tool as read-only (readOnlyHint=true). The description adds that it returns per-residue conservation scores and amino-acid probability distributions, which provides useful behavioral context beyond the annotations. However, it does not disclose other traits like performance, error handling, or output format details.

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, front-loaded sentence that efficiently conveys the tool's purpose and key output characteristics without extraneous 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?

Given the lack of an output schema, the description partially addresses return values by mentioning 'per-residue conservation scores and amino-acid probability distributions', but it does not specify the structure, format, or any additional context about the data.

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?

Input schema coverage is 100% with both parameters (pdb_id, entity_id) having descriptions. The description adds no further meaning beyond what the schema provides, so baseline score of 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 states the tool returns residue-level sequence conservation data for a specific PDB entry and entity, including per-residue scores and probability distributions. It distinguishes itself from sibling tools like the Uniprot conservation endpoint by specifying 'PDB entry ID' and 'PDB entity ID'.

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 by specifying the required parameters (pdb_id, entity_id), but it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. No guidance on prerequisites or limitations.

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