Pursue to an Order Confirmation

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

Annotations already indicate it's a write operation (readOnlyHint false) and non-destructive. The description adds the endpoint mapping and states 'create,' which is consistent. It does not add further behavioral details like idempotency or error modes, so it is adequate but not enhanced.

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 defines purpose and prerequisite, the second gives the API mapping. Ideal conciseness.

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 two-parameter create tool with openWorldHint and no output schema, the description is largely complete. It explains the purpose, prerequisite, and endpoint. It could mention that the operation is not idempotent, but overall it provides enough context for correct usage.

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?

Both parameters have descriptions in the schema (100% coverage), so baseline is 3. The body description references another tool for shape, which adds some value, but does not provide the full schema. This is sufficient given the open world hint.

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 creates a new order confirmation as a follow-up to a preceding quotation, with a specific verb and resource. It distinguishes from sibling pursue tools (e.g., pursue_invoice) by mentioning the quotation prerequisite and the endpoint.

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 indicates when to use (after a quotation) and provides the endpoint. It could explicitly mention not to use when no preceding quotation exists or contrast with lexware_create_order_confirmation, but the context is clear enough for an agent.

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