delete_store_order_line

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

Discloses destructive behavior ('cannot be undone'), rate limit (max 10 concurrent requests), and respect for read-only/dry-run modes. Annotations already indicate idempotent and destructive hints, and description adds useful context without contradiction.

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 concise and well-structured: a single-sentence summary, followed by behavioral details, then parameter descriptions. No redundant 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?

Covers all critical aspects: purpose, usage context, parameter semantics, return value, and behavioral notes. The presence of an output schema is complemented by the description of the return format.

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?

Since schema description coverage is 0%, the description fully compensates by explaining each parameter's purpose (store_id, order_id, line_id) and providing guidance on how to obtain them (e.g., 'Obtain from list_ecommerce_stores'). The optional account parameter is also well-documented.

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 'Permanently delete a line item from an e-commerce order,' specifying the verb, resource, and context. It distinguishes from siblings like delete_store_order and create_store_order_line.

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?

Provides context on when to use (manual e-commerce stores) and warns about permanence. Mentions authentication and rate limits but does not explicitly list when not to use or alternatives.

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