save_invoice

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

The description correctly implies mutation ('save/create'), aligning with the destructiveHint=true annotation. However, it does not elaborate on the create vs update behavior (invois_id=0 creates, otherwise updates), which is critical context beyond what annotations 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?

The description is very short and front-loaded, consisting of a single sentence with a helpful Georgian translation. It is concise with no wasted words, though it could be slightly more informative.

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?

Given the tool has 7 parameters (4 required) and no output schema, the description is insufficient. It omits critical details like return value, the create vs update mechanism, and any constraints. The agent would be left guessing about the tool's behavior beyond the basic action.

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 already covers all 7 parameters with descriptions (100% coverage), so the description adds no additional meaning. Baseline 3 is appropriate as the schema does the heavy lifting.

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 verb 'Save/create' and resource 'tax invoice', making the purpose identifiable. However, it fails to differentiate from sibling tools like save_invoice_a or save_invoice_desc, which could lead to confusion.

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 guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or scenarios mentioned. The agent receives no help in deciding between this and similar save_invoice variants.

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