Generate Palette PDF

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

The readOnlyHint annotation indicates a non-mutating operation, and the description confirms by stating it 'Returns a downloadable PDF' without mentioning side effects. The description adds behavioral context beyond annotations, such as the required entry fields and the PDF contents, enhancing transparency.

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 four concise sentences. The first sentence states the core purpose, the second lists PDF contents, the third gives usage guidance, and the fourth states use cases. Every sentence adds value, and the structure is front-loaded with the most important information.

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 covers the tool's purpose, output, and parameter usage. Given the presence of an output schema, it does not need to explain return values. It also lists the PDF contents. However, it omits details about error handling or prerequisites (e.g., whether entries must be from the archive), but overall it is sufficiently complete for an agent to use correctly.

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?

With 100% schema coverage, the schema already describes parameters well. The description adds value by specifying that entries come from query_hex or palette_from_concept, giving examples for the query parameter (e.g., 'Ottoman imperial luxury'), and explaining the source default and variants ('brand, conceptual'), enhancing understanding beyond the schema.

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 generates a premium branded PDF specification sheet from palette entries. It specifies the action (generate), resource (palette of archive entries), and output (downloadable PDF with detailed colour data), distinguishing it from sibling palette tools that likely produce different formats or outputs.

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 context: 'Pass the entries array from query_hex or palette_from_concept directly' and 'Use this to create client deliverables, specification sheets, and print assets.' It implies when to use this tool (when a PDF is needed) but does not explicitly state when not to use it or mention alternatives, leaving a slight gap.

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