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 covered. The description adds that each result carries sources and credit, which is useful context beyond annotations, but it says nothing about ranking, result limits, or how the cursor behaves despite the pagination parameter.

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?

Two short sentences with no padding, and the core purpose is front-loaded. The second sentence is terse to the point of ambiguity ('credit' is undefined), so brevity costs a little clarity rather than adding it.

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?

With no output schema and 0% parameter coverage, the description carries the full burden and falls short: search scope, pagination behavior, and result shape are all unaddressed. For a search tool with a cursor parameter, this leaves real gaps an agent needs filled before calling it confidently.

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 both parameters: 'query' and 'cursor' are bare strings with no documentation. The description does not compensate — it never says what 'query' matches (titles, abstracts, full text) or that 'cursor' is for pagination, so an agent must guess at both semantics.

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?

States a specific verb ('Search') and resource ('stored PepBank findings'), so the agent knows this is a retrieval tool over a findings corpus. However, it never distinguishes itself from the sibling 'peptide_research' or 'search_products', leaving overlap for an agent to guess at.

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 'peptide_research', 'search_products', or 'get_product', and no prerequisites or exclusions. The second sentence describes output content, not usage context, so the agent gets no routing guidance.

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