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

No annotations are provided, so the description must disclose behavioral traits. It only says 'search', implying a read operation, but does not mention rate limits, authentication, return format, pagination, or any side effects. For a search tool, this is a thin disclosure, though it does not contradict annotations since none exist.

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 with no redundancy, which is efficient. However, it is so terse that it omits essential information about the query parameter and usage context. It is concise but under-specified, so it earns an average score.

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 tool with one parameter and no annotations, the description should at least explain the parameter and basic expectations. It only states the purpose, leaving the agent to guess how to construct a query or interpret results. Even with an output schema present, the input side is inadequately documented.

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?

The schema has one parameter 'q' with 0% description coverage, and the tool description does not explain what 'q' means. The name 'pubmed' and the phrase 'paper search' imply 'q' is a query string, but that is left to inference. The description fails to compensate for the missing schema documentation.

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 states a clear verb ('search') and a specific resource ('biomedical papers' via PubMed/NCBI). It distinguishes from generic web search and implies a biomedical scope, though it doesn't explicitly name alternatives like arxiv or semanticscholar. The purpose is identifiable without opening the schema.

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 guidance on when to use this tool versus sibling paper-search tools (e.g., arxiv, dblp, semanticscholar). The description does not mention preferred use cases, exclusions, or conditions that would select this tool over others. An agent must infer its relevance purely from the name.

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