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

Goes well beyond the annotations by disclosing concrete side effects: it replaces any existing quote from this supplier for the RFQ, appends a thread entry, and notifies the buyer by email plus an optional callback. It clarifies that repeating the call re-sends notifications, corroborating idempotentHint=false, and flags the authorization requirement.

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?

Three tight sentences, side-effect and prerequisite information front-loaded before the auth caveat, with no filler. Slightly dense but every clause carries required context.

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?

For a non-idempotent, destructive, open-world mutation with no output schema, the description covers authorization, side effects, and re-call behavior well. The main gap is parameter semantics, but the safety/behavior profile is complete enough to call 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 only 38% schema description coverage across 8 parameters, the description must compensate, but it only adds meaning to supplier_token (issued at company registration). Unit price, quantity, notes, lead time, and rfq_id semantics are left unexplained in both description and 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?

States a specific verb+resource (submit/answer a quote for an RFQ) and scopes the actor clearly ('for a manufacturer's agent'). An agent can distinguish this from sibling tools like submit_quote_request or create_rfq without opening a schema.

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?

Gives clear preconditions — the company must have been matched to the RFQ, the supplier token is required, and 'only call with the supplier's authorization'. It does not name alternative siblings or state when not to use it, keeping it short of a 5.

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