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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses pricing (flat $2.99/call, $1.99 with prepaid pack_code), the return format (report_pdf_base64 + full profile JSON), and output traits like 'honest confidence' and 'disclosed candidate conflicts.' It does not explicitly state side effects or permissions, but the read-only nature is implied and cost is a significant disclosure.

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 two sentences with high information density. Key deliverable is front-loaded, and pricing/pack_code details are relevant. The enumeration of report contents could be trimmed, but overall it is efficient and well-organized.

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, target audience, return format, and pricing. It does not mention prerequisites (e.g., whether a style_profile must already exist) or error handling for payment failures. Given the absence of an output schema, this is reasonably complete for a paid report tool.

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 63%, meaning several parameters (style, image_url, image_base64) lack descriptions. The tool description adds context about pack_code and pricing, but does not compensate for the undocumented parameters or clarify how images are to be supplied. It provides minimal value 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's function: rendering a style-profile analysis as a client-ready English PDF report with specific contents (palette, outfit formulas, draping boards) and returning it as base64 PDF plus JSON. It implicitly distinguishes itself as the final deliverable, but does not explicitly contrast with the sibling style_profile tool, so differentiation is present but not overt.

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?

It specifies the intended audience ('For agents serving human end-clients') and implies this is the polished output step, but does not explicitly state when to choose this over style_profile or when not to use it. No alternative tools or exclusion criteria are mentioned.

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