uniprot_compute_properties

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

Discloses computation methods (Lehninger pK, Kyte-Doolittle, Pace formula) and that it's pure-Python with no extra API calls, beyond annotations which already show readOnlyHint and openWorldHint. No contradictions.

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 is concise, listing properties and methods, but could be slightly more structured for readability.

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?

Covers what properties are computed, how, and the no-API-call aspect. Output schema exists for return values, so completeness is adequate for an agent to decide usage.

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?

With 0% schema description coverage, the description should compensate but does not explain the 'accession' or 'response_format' parameters beyond what the schema titles provide. No additional semantics added.

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 the tool computes derived sequence chemistry properties (molecular weight, pI, GRAVY, etc.) for a UniProt entry, distinguishing it from sibling tools that fetch data or features.

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?

Implies usage when these physicochemical properties are needed, and notes it uses only the canonical FASTA with no additional API calls. However, lacks explicit when-not-to-use or sibling alternatives.

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