Read Resource Text

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

With no annotations, the description carries the full burden. It states 'Extract plain text' but lacks details on whether the tool is read-only, if it modifies files, or the impact of parameters like 'max_chars' and 'save_download'.

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 a single, concise sentence that front-loads the action and purpose without extraneous words.

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?

Despite having an output schema, the description is insufficient for a 5-parameter tool with no annotations. It omits behavioral details and parameter roles, leaving the agent with incomplete guidance.

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 description adds value by explaining 'url' and 'path' as sources (Ninova URLs or local paths from download_resource), but with 0% schema coverage, it fails to clarify other parameters like 'filename', 'max_chars', and 'save_download'.

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 action ('Extract plain text') and the resource type ('Ninova PDF/DOCX/TXT or a local path from download_resource'), differentiating it from sibling tools like 'read_page' and 'download_resource'.

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?

The description implies usage for reading lecture notes and assignments but does not explicitly state when to use or avoid this tool compared to alternatives like 'download_resource' or 'read_page'.

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