export_data

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

Discloses it returns a complete backup of specified data. Implicitly non-destructive (read operation), though no explicit safety guarantee. Good context despite lack of annotations.

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 sentences with no wasted words. First sentence states purpose, second details contents, third mentions reimport. Information is front-loaded.

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?

Given no parameters and presence of output schema, description covers all essential behavioral aspects (what is exported, import capability). Complete for this tool's complexity.

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?

No parameters, so schema coverage is 100%. Description adds value by clarifying it exports 'all' user data with no filtering, which is meaningful beyond schema.

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?

Description explicitly states it exports all user data as JSON, a complete backup. Lists specific data types (tasks with full history, mood vectors, recurrence rules, root ordering, daily plans). Distinguishes from sibling import_data.

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?

Clearly indicates usage for backup purposes and mentions reimport via web UI. No direct when-not or alternatives, but context suggests export is for backup, import for restore.

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