fetch_article_details

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

No annotations are provided, so the description must convey behavioral traits. It only states the basic function and parameter formats. It does not mention authentication, rate limits, or the nature of 'detailed information' returned. The output_format parameter is not explained in the description.

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 concise, with a clear opening sentence, a well-organized list of pmids formats, and a short return statement. Every sentence adds value, and the structure is front-loaded. No unnecessary elaboration.

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 presence of an output schema and two parameters, the description covers the complex pmids parameter thoroughly but omits explanation of output_format and what 'detailed information' entails. Still, it is sufficient for basic usage.

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. The description adds significant meaning for the pmids parameter by listing multiple accepted formats (string, list, integer, prefix). However, it does not describe the output_format parameter beyond what the schema provides via enum. This imbalance still adds substantial value overall.

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 verb 'fetch' and resource 'detailed information for one or more PubMed articles.' It specifies that it handles multiple PMIDs, distinguishing it from siblings like get_fulltext (for full text) or get_article_figures (for figures). The purpose is unambiguous.

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 explicit guidance on when to use this tool versus alternatives like get_cached_article or get_fulltext. The description implies it is for general article details, but does not state when not to use it or name sibling tools for specific use cases.

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