delete_subtotal_position

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive operation. The description adds no additional context beyond the verb 'delete', such as irreversibility, cascading effects, or permission requirements, so it contributes little beyond the structured metadata.

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 a single, concise, and easily parseable sentence. It is not a tautology and effectively communicates the core action, though it could be slightly expanded with usage context without losing 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 simple delete tool with a complete schema and clear annotations, the description provides the essential purpose. However, it lacks usage context such as which document types it applies to and how it relates to other position deletion tools, making it minimally viable but not 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 description coverage is 100%, and the schema itself provides clear explanations for each parameter, including the relationship between kb_document_type and document_id. The description adds no parameter-level information, so it meets the baseline but does not elevate the semantics.

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 the action ('Delete') and the resource ('a subtotal position'), which differentiates it from sibling tools like delete_subposition or delete_item_position. However, it does not explicitly mention the supported document types (offer, order, invoice), which are only found in the schema.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites, exclusions, or context such as that it applies to specific document types. With many sibling delete tools, this lack of direction makes it hard for an agent to select it confidently.

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