create_pdf_tool

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

There are no annotations clarifying side effects. The description only says 'generate' without disclosing whether files are written to disk, whether existing files are overwritten, or if any system modifications occur. The presence of parameters like 'overwrite' and 'output_directory' is not reflected in the description, leaving behavioral aspects opaque.

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, comprising one sentence plus examples. It conveys the core function without unnecessary detail or redundancy, making it easy to read and understand.

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 is minimal and does not cover the full scope of the tool's capabilities. It omits explanations of key parameters, the meaning of 'test fixture', the output behavior, and any prerequisites. Given the 8-parameter schema and potential for file system interactions, the description leaves significant gaps for the user.

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 description offers some hints about parameters via examples (pages, text, size), which partially aligns with schema fields like 'pages', 'text_per_page', and 'target_size_mb'. However, it does not explicitly map parameters or explain their meanings, leaving many fields (e.g., 'filename', 'overwrite', 'page_size') unaddressed.

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 purpose: generating a PDF test fixture with a specified number of pages. The examples (100 blank pages, 200-page PDF with sample text, ~30 MB PDF) provide concrete illustrations that reinforce the primary function and distinguish it from sibling tools like create_image_tool or create_dummy_file_tool.

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 indicate when to use this tool over alternatives. It implies usage for creating PDF test fixtures, but lacks guidance on scenarios where other file-creation tools might be more appropriate. No mention of when not to use it is provided.

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