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

With no annotations provided, the description fails to disclose critical behavioral traits: the return format (plain text, JSON, structured data?), file system side effects (what gets saved to save_path?), error handling for invalid IDs, or whether full text versus abstracts are returned. 'Extract text content' is the only behavioral hint.

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 single-sentence description is appropriately front-loaded with the core action, but it is excessively terse for a tool with file system interactions and specific ID requirements. It wastes no words, yet omits essential information that should have been included.

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?

Given zero schema coverage, no annotations, and no output schema, the description is inadequate. It lacks paper_id format specification, save_path behavior explanation, and return value documentation—critical gaps for a tool interacting with external APIs and local file systems.

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%—neither paper_id (is it PMID, DOI, or URL?) nor save_path (what format? creates directories?) are documented in the schema. The description completely fails to compensate by explaining these parameters, leaving both effectively undocumented.

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 clearly states the tool reads and extracts text from PubMed papers, distinguishing it from search tools and other sources (arxiv, biorxiv). However, it does not explicitly differentiate from the sibling 'download_pubmed' tool, leaving ambiguity about whether this tool returns text content directly versus saving a PDF file.

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?

No guidance is provided on when to use this tool versus 'download_pubmed' or how to obtain the required paper_id (e.g., via search_pubmed). There are no prerequisites, format examples, or 'when-not-to-use' exclusions mentioned.

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