Export To Json

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

With no annotations, the description carries the full behavioral burden. It discloses default behaviors (null/empty fields omitted), the effect of include_empty, the meaning of indent values, and even guarantees 'Always succeeds.' It also states the exact return shape, giving the agent strong expectations beyond 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 compact yet information-dense, with no filler. It front-loads the core purpose, then logically covers sequencing, parameter behavior, and return value. Every sentence adds useful operational detail, and the length is appropriate for a three-parameter serialization tool.

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 fully covers what the agent needs to call the tool correctly: when to use it, what input it expects, how each parameter behaves, and what it returns. The explicit 'Always succeeds' note removes ambiguity about failure modes. Despite lacking annotations, the description is self-sufficient and complete.

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, but the description adds meaningful context: it explains why null/empty fields are omitted by default, gives concrete indent examples (0=compact, 2=standard, 4=wide), and clarifies how include_empty changes output. This enriches interpretation beyond the schema's short field descriptions.

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 a specific verb and resource: 'Serialize a parsed FatturaPA dict to a clean, indented JSON string.' This clearly distinguishes the tool from XML-generation and parsing siblings such as generate_fattura_xml and parse_fattura_xml. The purpose is unambiguous and immediately actionable.

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 instructs when to call the tool: 'Call this after parse_fattura_xml() when you need a human-readable or machine-transferable representation of the invoice.' This provides clear sequencing and context, though it does not explicitly mention when-not-to-use it or name alternative serialization tools.

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