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

With no annotations, the description carries full burden. It discloses soft-delete, restorability by Admin, blocking conditions, and preview/confirm behavior. Missing details on auth requirements or error states, but covers the key behavioral traits.

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 sentences, front-loaded with main action, then condition, then behavior. No filler words. Every sentence adds critical information.

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?

No output schema, so description should explain return values. It mentions 'Returns a preview' but doesn't specify what the preview contains or the success response format. Also lacks error scenario handling (e.g., order not found). The blocking condition is well-stated, but overall completeness is adequate but not thorough.

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 100%, so baseline is 3. Description adds value by explaining the confirm parameter's preview mode and the idempotency behavior. No extra info on frame_order_id beyond schema, but the preview context is useful.

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?

Description clearly states the action ('Soft-delete an Open frame order'), specifies it's restorable by an Admin, and differentiates from other deletion tools like permanent_delete_entity by emphasizing it's a soft-delete. Also distinguishes from close_frame_order by noting it's a deletion.

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?

Explicitly states when the tool is blocked (if Issued/Sent/Paid invoices are linked) and provides prerequisite actions (void or unlink them). Also explains preview behavior vs confirmation. Lacks explicit mention of when to use this over permanent_delete_entity or restore_entity, but the soft-delete and admin-restorable context implies it.

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