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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral detail by saying results carry the paper's verdict, summary, and review link. No contradictions or hidden behaviors are apparent.

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?

Three focused sentences, with the core action front-loaded and no filler. Each sentence adds distinct value: what is searched, when to use it, and what results contain.

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 lightweight read-only search tool with only two parameters and an output schema, the description covers the invocation trigger, search scope, and result contents. Nothing essential is missing for an agent to call this tool correctly.

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 coverage is only 50%: the query parameter is described well in both schema and description, but the limit parameter has no description in the schema and is not mentioned in the description. The description reinforces query intent but does not add meaning for limit or explain its effect on results.

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 action ('Search Pith-reviewed papers') and a clear resource ('papers by title and abstract'). It also gives concrete user intents (topic, phenomenon, method, paper title) that map to this tool, distinguishing it from sibling claim/passage/citation tools.

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 explicitly states when to call the tool: when a user names a research topic or asks whether Pith has reviewed a subject. It also provides an exclusion ('without an identifier'), but it does not name alternatives like search_claims or resolve_paper, so the routing guidance is good but not complete.

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