Export collected data

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description usefully adds that the export is un-paginated and returns the FULL table, which warns the agent about potentially large payloads, but it says nothing about auth requirements, size limits, or whether filters must be set to avoid huge results.

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?

A single front-loaded sentence with no filler; the key behavioral fact (un-paginated, filter-applied full table) is surfaced immediately.

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 five mostly-undescribed parameters, no output schema, and no indication of which identifiers are required, the description leaves an agent guessing how to target the right workflow and what the returned payload looks like. Given the low schema coverage, it needed to compensate more than it does.

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 only 20% — just 'format' is documented, and the description only restates csv/json. The meaning of q, view, workflow and workflow_id (and which of the redundant workflow/workflow_id to use) is left entirely undocumented despite 5 parameters and zero required fields.

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 (Export) and resource (a workflow's full extracted-data table) plus the output formats, so an agent knows exactly what it produces. It doesn't explicitly distinguish itself from close siblings like writ_workflow_data or writ_search_data, which is the only reason it isn't a 5.

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?

'search/filter applied, un-paginated' implies this is the bulk-export counterpart to a paginated/search tool, but no alternative is named and no when-to-use or when-not-to-use condition is given. Usage must be inferred from the parenthetical.

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