create_subtotal_position

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

Annotations already indicate a write operation (readOnlyHint=false), but the description adds no behavioral context beyond the word 'create'. It does not disclose any side effects, requirements, or ordering behavior, which are relevant for a mutation tool.

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 extremely short but this is under-specification rather than appropriate conciseness. It provides no structural breakdown or detail, consisting only of a single tautological phrase.

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?

This tool lacks an output schema and has only a one-line description. There is no explanation of what a subtotal position is, how it fits into a document, or any preconditions. An agent would not have enough information to use this tool correctly or know when it is appropriate.

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?

The input schema already provides clear descriptions for the required parameters (document_id and kb_document_type), covering the main semantics. The optional 'text' parameter is undocumented but self-explanatory. The description itself adds no parameter information, but the schema does most of the heavy lifting.

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 'Create a subtotal position' merely restates the tool name and provides no additional meaning. It fails to explain what a subtotal position is or how it differs from sibling position creation tools like create_item_position, create_discount_position, or create_text_position.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention which document types it applies to (though the schema enum shows quotes, orders, invoices) or any prerequisites or exclusions.

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