export_responses

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

Describes key behavioral traits beyond annotations: auto-saving large exports to local file to avoid context limits, and that small exports are returned directly. Does not cover potential performance implications or exact file location details.

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?

Three concise sentences. First sentence states purpose, second highlights critical auto-save behavior with emphasis, third provides alternative. No wasted words.

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?

Covers main functionality and guidance. Lacks explicit description of return values for small exports (direct response format), but given no output schema, this is acceptable. Provides enough for an agent to use correctly.

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?

Adds meaning beyond schema by explaining the auto-save behavior, recommending 'saveToFile', and noting the format options. Schema has 100% coverage, but description provides extra context and usage advice.

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?

Clearly states 'Export survey responses in JSON or CSV format', specifying verb and resource. Differentiates from sibling 'export_responses_filtered' by mentioning it for better control over data size.

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?

Explicitly recommends 'export_responses_filtered' for filtered exports, explains auto-save behavior for large exports, and advises using the 'saveToFile' parameter for easier access.

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