read_openaire_paper

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

Without annotations, the description bears full responsibility. The word 'Attempt' hints at possible failure, but it does not disclose side effects (e.g., whether it downloads the PDF), error handling, or required permissions. The return type is minimally described as 'Extracted text or error message'.

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 and follows a docstring structure with 'Args' and 'Returns'. It is efficiently written, though the opening phrase 'Attempt to' could be more direct.

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 abundance of sibling read tools and the lack of annotations, the description is insufficient. It omits key behavioral details (e.g., download behavior), format constraints, and does not help the agent choose among similar tools.

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 coverage is 0%, so the description adds value by naming parameters and providing brief explanations (e.g., 'OpenAIRE paper identifier' and 'Directory where the PDF is/will be saved'). However, the format of 'paper_id' is unspecified, and 'save_path' hints at a download side effect not clearly explained.

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 function ('read and extract text content') and the resource ('OpenAIRE paper'). However, it does not differentiate among sibling read tools, missing an opportunity to specify what makes OpenAIRE distinct.

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 other read tools or download tools. The description does not mention prerequisites, alternative tools, or ideal scenarios.

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