create_stock_item

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

No annotations, so the description carries the full burden and it does not mention that this writes to Tally, that a backup is taken, or that dry_run exists for safe previews. For a mutation tool with real side effects this is a significant omission.

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?

A single efficient sentence with no filler and no burying of key information. It is arguably too short rather than bloated, so conciseness itself is well handled.

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?

An 18-parameter mutation tool with no annotations and no output schema needs far more: validation rules, defaults, units prerequisite, dry_run workflow, and what a successful response contains. The description is a field list, not an operational brief.

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 description names roughly 5 of 18 parameters and only restates schema field names rather than adding meaning. With schema coverage at 56%, the undocumented half (aliases, cess_rate, taxability, extra_xml, opening_godown, dry_run) receives no compensating explanation in the description.

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?

Specific verb ('Create') plus resource ('stock item') and it enumerates the salient fields, so the agent knows exactly what will be produced. It stops short of differentiating itself from siblings like create_master or alter_stock_item, which is a meaningful ambiguity here.

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?

No statement of when to use this versus alter_stock_item, create_master, or import_raw_xml, all of which could plausibly create master data. No prerequisites (e.g. unit must exist first) appear in the description, only buried in the schema for one parameter.

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