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

Because no annotations are provided, the description carries full responsibility for behavioral disclosure. It does add meaningful context with 'Free. No inventory held here. Merchant stays merchant of record,' clarifying cost, fulfillment scope, and commercial role. However it omits important behaviors such as authentication, idempotency, persistence guarantees, or side effects beyond recording.

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 very brief and front-loaded, with the core action first followed by three short constraint phrases. Every sentence adds some contextual value, though some phrasing is cryptic. The compactness works in its favor, but it sacrifices clarity needed for a complex tool.

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 tool with 12 parameters, 5 required, no output schema, and no annotations, the description is far too thin to provide adequate context. It gives the high-level purpose and a few constraints but does not explain required inputs, return behavior, or how this tool fits into the overall offer/intent workflow. An agent would still face significant uncertainty when trying to call it 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?

Schema description coverage is 0%, so the description must compensate by explaining parameter meaning. It only hints at the 'spec' parameter through 'against a spec hash' and loosely implies price/quantity via 'vendor ask,' but none of the 12 parameters are actually described. This is not enough for an agent to confidently fill in required fields like merchant_url, ships_to_country, or unit_price_usd.

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 states a specific action and resource: 'Record a vendor ask against a spec hash.' This clearly communicates the tool's primary function and suggests a vendor-side offer action, which helps differentiate it from buyer-oriented siblings like post_intent. However, it does not explicitly name or contrast siblings, so it stops short of full differentiation.

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 implies the tool is for vendor asks and not inventory holding, but it gives no explicit when-to-use or when-not-to-use guidance and does not reference any sibling tool. An agent would have to infer the correct context from the tool name and sibling list rather than from actual routing instructions.

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