search_pubmed

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

No annotations provided, so description bears full burden. It only states 'Search PubMed' without disclosing rate limits, authentication needs, result format, or pagination behavior. Insufficient for a public API tool.

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 clear sentence with no wasted words. Front-loaded with purpose, efficiently covering action, resource, and parameter hints.

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 simple one-parameter tool, description is minimally adequate. However, lacks output format details, and no output schema is provided. Adequate but leaves agent guessing about return structure.

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 covers the 'term' parameter fully. Description adds value by providing examples ('drug name, condition, etc.'), going beyond the schema description. Baseline 3 plus enhancement yields 4.

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?

Description clearly states the verb 'Search' and resource 'PubMed for scientific papers', with examples of terms like drug name or condition. It distinguishes from sibling tool 'search_clinical_trials' by specifying scientific papers.

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 context (searching by term) but provides no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or limitations despite having sibling search_clinical_trials.

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