get_pdf_page_count

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether it is read-only, performance characteristics, size limits, or error handling beyond a straightforward page count. The minimal description leaves uncertainty.

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 well-structured with clear sections for args and returns. It avoids unnecessary words, though it could be more structured with examples or constraints.

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?

The description covers the basic purpose and input meaning, but given no annotations and a simple single-parameter tool, it is adequate. However, it lacks information on output format details (even though an output schema exists) and edge cases, making it only moderately complete.

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?

Although schema description coverage is 0%, the description explicitly states 'pdf_base64: Base64-encoded PDF file,' adding semantic meaning beyond the schema's type string alone. This helps the agent understand the input format.

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 'Get the total number of pages in a PDF' clearly states a specific verb (get) and resource (page count of a PDF), distinguishing it from sibling tools like get_pdf_metadata or extract_text_from_pdf.

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, such as when only metadata is needed or when page count is part of a larger extraction task. The description does not provide usage context or exclusions.

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