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

With no annotations provided, the description carries the full burden. It discloses that a download link expires within ~48 hours and that nothing submitted is stored, which is valuable behavioral and privacy context. This goes beyond the schema's capabilities.

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, front-loaded with the primary action, and efficiently packs in output details, input requirements, expiry behavior, and privacy. No wasted words.

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 essential workflow: input (parsed line items, company name), output (download link with expiry), and content (grouping, pricing columns, terms). Since there is no output schema, this return-value description is important and it is provided. The schema handles parameter details, so the combination is quite complete.

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 high at 88%, so the baseline is 3. The description adds high-level pointers to line items and company name but doesn't explain individual parameters beyond what the schema already documents. It does not compensate for the small unexplained gap, but the schema carries most of the weight.

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 begins with 'Generate a vendor-ready Request for Quotation (.xlsx)' – a specific verb, resource, and format. It further clarifies the output structure (grouped by material, vendor pricing columns, totals, standard terms) and clearly distinguishes from all sibling tools, none of which generate RFQs.

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 states 'You pass parsed line items and a company name', providing clear input context. It doesn't explicitly name alternatives, but no sibling tool performs a similar function, so the guidance is adequate. The mention of 'standard terms' also implies a default use case.

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