render_pdf_page

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

No annotations provided, so description must carry behavioral disclosure. It correctly implies a read-only rendering operation with no mention of side effects. However, it does not explicitly state safety (read-only, no modifications) that annotations would have provided. Lacks details on potential issues like size or time, but for a simple tool it's minimally adequate.

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?

Two sentences, front-loaded with the core action. Efficient and no wasted words, though could include parameter details without harming conciseness.

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?

With 3 parameters, no schema descriptions, no annotations, but an output schema exists, the description is partially complete. It states the purpose and when to use but lacks parameter explanations and return format details. The output schema might cover return values, but the description itself is insufficient for full understanding.

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%, and description provides no explanation of parameters ('doc_id', 'page', 'dpi'). It does not clarify page numbering (0- or 1-based), what doc_id refers to, or the effect of dpi. Description fails to compensate for the lack of schema descriptions.

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?

Description clearly states verb 'render', resource 'PDF page', output 'PNG evidence image'. Distinguishes from sibling tools that extract specific elements like figures, tables, etc. by stating 'beyond extracted figures, tables, images, or formulas'.

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?

Explicitly says when to use: 'when page-level visual evidence is needed beyond extracted figures, tables, images, or formulas.' Provides clear context and implies alternatives, though does not explicitly state when not to use.

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