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

No annotations are provided, so the description carries the full burden. It discloses that the tool normalizes up to 500 lines, does not submit or purchase, and returns a review link. This is clear behavioral context, though it could mention whether any state changes or side effects occur beyond returning a link.

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?

Two sentences with no wasted words. The first sentence states the core action and limit, the second clarifies what it does not do. Information is front-loaded and every sentence earns its place.

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?

With 2 parameters and no output schema, the description provides enough context: what the tool does, its limit, and its non-actions. It could mention the format of the review link or next steps, but given the simplicity, it is adequate.

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 50% (lines parameter has detailed schema but context less so). The tool description adds value by mentioning the 500-line limit and the normalization purpose, which gives context for the lines parameter. It does not explain the context parameter further, but the schema already has a description for it.

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 it normalizes BOM lines into Cintra's quote-ready format and returns a review link, with specific verb 'normalizes' and resource 'BOM lines'. It explicitly differentiates from submission and purchase, and the sibling tool 'submit_quote_request' confirms this distinction.

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 says 'This does not submit, purchase, reserve inventory, or create a binding quote,' which tells the agent it is a preparatory step. It implies use before submit_quote_request, but does not explicitly name alternatives or provide when-not-to-use scenarios beyond the negation.

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