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

Annotations already declare readOnlyHint=true, so the agent knows it is a safe read operation. The description adds valuable behavioral context beyond this by disclosing the 'headless only' requirement and the base64 PDF return format. There is no contradiction with the annotations.

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 highly concise: two short sentences totaling 12 words. It front-loads the primary action and includes the key constraint and return type. Every word contributes meaning, with no redundant text or fluff.

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 tool has a simple interface (two optional params, no output schema), and the description covers the core purpose and return value. However, it omits parameter semantics, particularly valid format_ values, and does not mention what happens if used outside headless mode. For a tool this simple, it is adequate but has room for improvement.

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 schema has 0% description coverage and the description does not mention either parameter (format_ or landscape). This leaves format_ ambiguous (e.g., what string values are accepted?) and requires the agent to rely on parameter names alone. Since the description does not compensate for the schema's lack of explanation, this is a significant gap.

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 tool's function: render the current page as PDF. It uses a specific verb ('Render') and identifies the resource ('the current page'), which distinguishes it from sibling tools like screenshot or get_html. The 'headless only' constraint and the return format are also specified, leaving no ambiguity about what the tool does.

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 provides clear context by noting that the tool is 'headless only', which serves as an exclusion when the browser is not in headless mode. While it does not explicitly name alternative tools, the phrase 'headless only' guides the agent on when not to use this tool, and the purpose itself implies its use for PDF generation.

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