generate_pdfs_async

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

Annotations already indicate readOnlyHint=false (write operation) and destructiveHint=false. The description adds behavioral context: 'Immediately returns requestId and files information,' clarifying the async nature and immediate response. It does not contradict 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 concise, front-loaded with the primary function, and contains no unnecessary words. The important warning section is separate and clearly marked. Every sentence adds value.

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 complexity (multiple PDFs async), the description covers key aspects: async behavior, immediate return, prerequisite steps, and referral to another tool for ZIP. It lacks detail on the response structure beyond 'requestId and files information,' but this is adequate given no output schema. Annotations and schema fill remaining gaps.

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 coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining that the 'params' field should be structured based on get_design_parameters, and it highlights the required 'fileName' and 'params' fields. This guidance is crucial for correct parameter usage.

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: 'Generates multiple PDFs asynchronously with multiple parameter sets.' It specifies the verb 'generate', the resource 'multiple PDFs', and the asynchronous mode. It also distinguishes from siblings by explicitly mentioning the download_zip tool for ZIP downloads and implying sync versions exist.

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 explicit usage guidelines: before calling, use get_design_parameters to check required parameters, ask the user for missing values, and never generate placeholders. It also directs the user to download_zip for ZIP downloads, offering clear when-to-use versus alternative tools.

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