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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds genuine value by enumerating the response contents (summary, main findings, sources, credit), but says nothing about what happens with an unknown peptide name or how errors surface.

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?

One front-loaded sentence with no filler, and the returned content is listed immediately. The only weakness is the unexplained term 'credit', which is jargon an agent cannot interpret without the schema.

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?

For a one-parameter read-only lookup with full annotations and no output schema, the description covers purpose and roughly what is returned. It falls short on the parameter's accepted format and on how this tool relates to search_research, both of which an agent needs to call it correctly the first time.

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 0% for the single required parameter, so the description carries the full burden and largely fails: it never says whether 'peptide' is a name, a PepBank ID, or a sequence, nor whether matching is exact or case-sensitive. Only the implicit association with 'PepBank peptide' gives any hint about the accepted value.

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 names a specific verb ('Read') and a specific resource ('a PepBank peptide summary, main findings, sources, and credit'), so an agent knows exactly what it gets back. It does not, however, distinguish itself from the sibling search_research, which an agent could easily confuse with this lookup.

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?

There is no statement of when to use this tool versus search_research or get_product, and no prerequisites or exclusions. Usage is only implied by the phrase 'PepBank peptide summary', leaving the agent to infer the call context.

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