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

Annotations indicate a write operation but not destructive. The description adds the crucial side effect that points are deducted immediately, which is not present in annotations. This goes beyond structured data and alerts the agent to a significant consequence.

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 fluff. The purpose and the critical warning are front-loaded, and every word 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?

For a tool with 6 parameters and no output schema, the description covers the essential flow but omits any information about the return value or error conditions. It also doesn't explain the role of formData and templateOption, though these are partially in schema. Adequate for the core behavior but not fully comprehensive.

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 coverage is 83%, so most parameters have descriptions. The description adds the requirement that confirm must be true after user confirmation, but does not clarify formData or templateOption beyond schema. It adds marginal value over the 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 action (create order) and explicitly labels it as step 2 of the order flow, distinguishing it from quote_order and other order-related siblings. The title '포인트 주문 확정' reinforces the purpose.

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 usage context: it is the second step after quote, and requires user confirmation before calling with confirm:true. It also warns about immediate point deduction, which is a key decision factor. However, it does not explicitly name alternative tools or conditions for not using it.

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