get_pdf_page_info

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

With no annotations provided, the description carries full burden. It discloses that the tool returns a dictionary with specific fields but does not mention if it is read-only, requires file permissions, or handles errors. Basic disclosure is present, but more detail on behavioral traits is missing.

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 structured with Args and Returns sections, making it easy to parse. It is not overly concise but is well-organized and front-loaded with the purpose. Could be slightly shortened without losing clarity.

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 tool's simplicity (2 required params, no output schema), the description adequately explains parameters and return values. However, it lacks information on error handling or edge cases (e.g., invalid path or page number).

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 fully explains both parameters: 'file_path: PDF文件的完整路径' and 'page: 页码（从1开始）', adding clear meaning beyond just names and types.

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 '获取PDF指定页面的详细信息' (get details of a specified PDF page), specifying the verb 'get' and the resource 'PDF page info'. It distinguishes this tool from siblings like 'get_pdf_info' (which likely covers the whole document) by focusing on a single page's detailed properties.

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 does not explicitly state when to use this tool versus alternatives. It implies usage for getting detailed page info but lacks guidance on prerequisites, exclusions, or conditions where another sibling would be more appropriate.

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