Ler PDF (texto)

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

With no annotations, the description carries the behavioral burden and does so clearly: it discloses a read-only extraction operation, a text return type, and character-based pagination rather than page-based pagination. It does not cover edge cases like scanned PDFs or error behavior, but the core behavioral profile is transparent.

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 two compact sentences with the core action front-loaded and pagination behavior stated immediately. There is no filler, repetition, or unnecessary schema echo.

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?

For a simple read operation with three parameters, the description adequately covers what is extracted, where the operation applies, and how pagination works. Since there is no output schema, a slightly more explicit statement of the return shape would help, but an agent has enough context to invoke the tool correctly.

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%, so the description must compensate. It adds meaningful semantics by specifying that offset/limit count characters rather than pages and that the target is a PDF inside the workspace. The required path parameter could be described more explicitly, but the most ambiguous pagination parameters are clarified.

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 uses a concrete verb and resource: it extracts text from a PDF in the workspace. The PDF-specific scope distinguishes it from sibling readers like read_docx and read_sheet, and the pagination note adds further specificity.

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 intended use case is implied by the tool name and description, but there is no explicit comparison to siblings such as read_file or read_docx, and no when-not-to-use guidance. An agent can infer when to use it, but the description does not actively route it away from alternatives.

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