create_stock_group

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

Annotations indicate readOnlyHint: false, and the description aligns by stating 'Create a new Stock Group'. It adds context about the relationship to stock items, but does not detail side effects like idempotency or error behavior; annotations already cover the read-only aspect, so the bar is met.

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 concise—three sentences—and well-structured: it states the purpose, distinguishes from a sibling, and gives a prerequisite. No unnecessary information is included.

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?

The description includes the prerequisite relationship (required before creating a stock item) and clarifies the distinction from account groups. It does not mention the return type or error handling, but given the absence of an output schema, the context is sufficiently complete for an agent to decide when to invoke it.

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 provides descriptions for both parameters (name and parent), achieving 100% coverage. The tool description does not add extra semantics beyond what the schema already states, so the baseline score of 3 is appropriate.

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 purpose: to create a new Stock Group in TallyPrime. It also distinguishes it from the sibling create_group (account groups) and specifies its role as the category for stock items, making the tool's intent unambiguous.

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 explicitly provides usage conditions: it is required before creating a stock item under a new category, and it contrasts with create_group, giving clear guidance on when to select this tool over alternatives.

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