get_europepmc_pdf_as_markdown

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

With no annotations, the description must disclose behavior. It says 'without file saving', implying in-memory conversion, but doesn't mention network dependency, output format details, or error handling. Minimal transparency.

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 is concise but overly terse. It conveys the main purpose but omits essential details, sacrificing completeness for brevity.

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 5 parameters (1 required), no output schema, and no annotations, the description is severely incomplete. It fails to explain input requirements, parameter usage, or return format, leaving the agent to guess.

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%, yet the description provides no explanation for any of the 5 parameters. 'identifier' is required but undefined; 'extract_tables', 'processing_method', 'offset', and 'limit' are completely unexplained.

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 'Convert PDF to Markdown without file saving', which clearly identifies the action and resource. While it lacks explicit mention of Europe PMC, the tool name and sibling context imply that. It distinguishes from siblings like 'get_europepmc_full_text' (likely XML) and 'search_europepmc_papers' (search).

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 on when to use this tool versus alternatives like 'get_europepmc_full_text'. No context on prerequisites for the identifier parameter or when conversion is appropriate.

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