tabular_document_save

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

With no annotations, the description carries the full behavioral burden, and it does so well by disclosing that saving can block a thin client and that interface_blocked=true requires waiting with client_busy_status or wait_client_idle. It also mentions the need to verify saved state and output path. It does not detail failure behavior or file-overwrite semantics, but the key operational risks are covered.

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 and every sentence earns its place: purpose, preference, success-confirmation requirement, and blocking behavior. It is front-loaded with the core purpose and then adds necessary operational details without redundancy.

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 tool has 7 parameters, no annotations, no output schema, and 0% schema description coverage, yet the description explains almost none of the parameters. While it provides useful behavioral guidance, an agent still lacks essential information about what each argument means and what values are valid, so the overall description is not complete enough for confident invocation.

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 0% across 7 parameters, and the description does not explain name, path, title, session_id, watchdog_timeout, or exact_filter_only. The only weak connection is 'selected format' alluding to the format parameter, but no formats or semantics are given. This is a major gap for an agent attempting to invoke the tool correctly.

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 clear verb and resource: saving a tabular document field to a file in a selected format. It also explicitly distinguishes this from reading a large report cell by cell, which differentiates it from sibling tools like tabular_document_text.

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?

It gives explicit when-to-use guidance by recommending this export over reading a large report cell by cell. It also provides operational guidance on confirming the returned saved state and output path before reporting success, plus when to wait during UI blocking.

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