create_group

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

Annotations establish that this is not read-only and is not idempotent, so the description correctly conveys a mutating operation. It adds the dual create/rename behavior, which is useful, but it does not disclose consequences such as duplicate-name behavior, whether renaming affects related ledgers, or what happens if the parent group is missing.

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 concise sentence that front-loads the core action and immediately clarifies the two operational modes. Every phrase earns its place, with no filler or repetition of already-structured schema details.

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 three-parameter create/update tool with no output schema, the description covers the essential decision point (oldName) and the meaning of parent. It is slightly thin on failure modes and side effects, but the schema plus this description are sufficient for an agent to invoke it correctly in most cases.

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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that 'parent' establishes nesting and that oldName switches the operation to rename/reparent, which directly clarifies parameter usage in context.

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 action: creating a new account group nested under a parent, with an explicit alternative mode to rename/reparent an existing group via oldName. It names the specific resource type ('account group in TallyPrime') and distinguishes itself from read-oriented siblings like get_groups and other create_* 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?

The description gives a clear behavioral condition: pass oldName to rename/reparent rather than create a new group. It implies the default use case (new group) but does not explicitly mention alternatives like list groups first with get_groups or use create_stock_group for stock groups, so it is clear but not exhaustive.

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