create_godown

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

Beyond annotations, the description discloses a live-confirmed behavioral gotcha: pass the parent's plain name, not a dotted path, with a concrete invalid/valid example. It also reveals the downstream failure mode if creation is skipped, giving the agent operational knowledge that the schema and annotations do not provide.

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?

Three sentences, each earning its place: what the tool does, when it is needed, and the critical path-format rule. The core purpose is front-loaded and no content is wasted.

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 two-parameter create tool with no output schema and no nested objects, the description covers purpose, prerequisite timing, failure symptoms, and the parameter format pitfall. Nothing essential for selecting and correctly invoking the tool is missing.

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?

Although schema coverage is 100%, the description adds critical meaning to the 'parent' parameter by explaining plain-name versus dotted-path usage and giving a concrete example: 'MAIN LOCATION' as parent + 'DUBAI' as name. This substantially reduces the risk of misformatted invocations.

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 opens with 'Create a new Godown/Location in TallyPrime', naming a specific verb and resource, and clarifies optional nesting. This clearly distinguishes it from sibling create_* tools like create_ledger, create_group, and create_stock_item, as well as the get_* read tools.

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?

It provides a clear trigger: use before referencing a godown that doesn't yet exist on an invoice/voucher line, otherwise the call fails with 'Godown does not exist!'. It does not explicitly name alternative tools or state when-not-to-use conditions, so it falls just short of a 5.

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