import_raw_xml

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

With no annotations, the description carries the full behavioral burden. It reveals that raw XMl can perform Create/Alter/Delete actions, which signals mutation and possible destruction, but it does not mention backup behavior, validation bypass, permissions, or irreversibility; the dry_run safety detail exists only in the schema.

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, compact, front-loaded sentence. It establishes the escape-hatch role first, then gives concrete XML examples, and ends with the routing preference, with no wasted text.

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 an advanced raw-import tool, the description does enough to route the agent correctly and clarify the XML payload shape. The schema covers parameters and dry_run behavior, but the description itself omits safety details that would matter for a destructive raw import path.

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 the schema already documents all four parameters. The description repeats the <TALLYMESSAGE> placement context and adds XML examples, but does not add meaning about report selection, company scoping, or dry_run beyond what the schema provides.

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?

States a specific verb and resource: import raw Tally XML objects, specifically the content inside <TALLYMESSAGE>, with examples such as <VOUCHER> or <LEDGER>. The phrase 'Advanced escape hatch' and 'Prefer the specific tools' clearly distinguishes it from the many create/alter/delete sibling 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 clear fallback guidance: this is an advanced escape hatch and callers should prefer the specific tools. It does not name those sibling tools explicitly or spell out precise exclusion cases, but the intended usage is still unambiguous.

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