app.export_json

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

No annotations are provided, so the description carries the full behavioral burden. 'Lossless internal model' is useful context, but it does not disclose whether existing files are overwritten, whether the document must be open, or what errors can occur when writing the path.

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 single sentence is front-loaded and waste-free. It is perhaps too terse for a file-export operation, but it avoids unnecessary repetition.

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?

With no annotations, no output schema, and an undocumented parameter, the description is incomplete for a tool that writes to disk. It does not cover file overwrite semantics, return behavior, or error conditions that an agent would need.

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?

There is one required parameter ('path') with 0% schema description coverage. The description only implies that 'path' is the destination JSON file, adding little beyond the parameter name and type.

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 states a specific verb and resource: 'Dump the document to a JSON file.' The parenthetical '(lossless internal model)' distinguishes this from lossy exports like app.export_png. However, it does not explicitly differentiate from app.save_document or app.save_document_as.

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?

Usage is implied by the format (' file') and the 'lossless' qualifier, but there is no explicit when-to-use guidance, no named alternative, and no prerequisite context for choosing this over save_document.

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