create_stock_item

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

Annotations already indicate this is a mutating, non-idempotent operation, but the description adds no behavioral detail beyond 'create'. It does not disclose what happens on duplicate names, whether existing stock items are replaced, whether Tally-side validation is performed, or what the caller should expect after invocation.

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, focused sentence with no filler or redundant elaboration. It is efficient and immediately readable, though minimal in scope.

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 9 parameters, no output schema, and many sibling creation tools, the description is too sparse. It omits necessary context like success/error behavior, required existing masters (e.g., group/unit), and the relationship to update_stock_item. The rich schema helps but does not compensate for the missing usage and outcome context.

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%, so every parameter is already well documented in the input schema. The tool description adds no parameter semantics, but the baseline of 3 applies because the schema carries the full burden and does so effectively.

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 verb ('Create') and the resource ('a new stock item in TallyPrime'), making the tool's basic function unambiguous. It is distinguishable from obvious siblings like update_stock_item and delete_stock_item by the word 'new', though it does not explicitly differentiate itself from other create_* tools beyond the resource name.

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, no mention of prerequisites such as the stock group or unit already existing, and no note about cases where update_stock_item or create_stock_group would be more appropriate. The usage is only implied by the tool name, which is insufficient given the large sibling set.

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