read_pubmed_paper

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

Despite the lack of annotations, the description explicitly states that the tool does not support direct paper reading, which is a key behavioral trait. However, it does not clarify why the tool exists or what the save_path parameter's purpose is (noted as unused), leaving ambiguity.

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 short and follows a standard docstring format. It is efficient but could be more concise by removing redundant structure for such a simple tool. Overall, it is appropriately sized.

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 the many sibling read tools, this description is complete in explaining that reading is not supported. However, it lacks context on why this tool exists and what the return string contains. The output schema exists but is not shown; the description notes a string return, which is adequate.

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 0% description coverage, so the description compensates by explaining paper_id as 'PubMed ID (PMID)' and save_path as 'Directory where the PDF would be saved (unused)'. This adds meaning but is minimal and the 'unused' note indicates a design flaw.

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 claims to 'read and extract text content' but then states it returns a message that direct reading is not supported. This is contradictory and misleads the agent about the actual functionality. It is not a tautology but fails to clearly communicate the tool's purpose.

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 alternatives like download_pubmed or read_arxiv_paper. The description implies it should not be used because it is unsupported, but does not suggest alternatives or conditions for use.

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