Export intake data

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

Description aligns with annotations (readOnly, idempotent, non-destructive) and adds critical context: omitted rows are reported, secrets/tokens are excluded, and CLI fallback exists. No contradictions.

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?

Two efficient sentences with no wasted words. Front-loads purpose and key features. All information is relevant and earnestly placed.

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?

For a read-only export tool with no output schema, description covers return format, row limiting, privacy, and fallback CLI. Adequately prepares agent to invoke 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?

Despite 60% schema coverage, description adds value by explaining rationale for since/until/max_rows (keep response small) and mentions omitted row reporting not in schema. Export_format and response_format are adequately covered by schema enums.

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 specifies exact verb 'Export', resource 'local intake data', format 'JSONL or CSV', and privacy feature 'without provider secrets or tokens'. It clearly distinguishes from sibling tools like nourish_list_intake and references CLI for full dump.

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 states default behavior (500 most-recent rows), how to refine via since/until/max_rows, and when to use the alternative CLI for unbounded export. Provides clear context for agent decision-making.

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