export_taskpaper

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

Discloses lossy nature of export, lists downgraded/omitted items, mentions lossiness warnings in meta.warnings, and states no side effects. No annotations provided, so description carries full burden and does so well.

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?

Concise at 5 sentences, front-loaded with main purpose, uses clear structure with quoted scopes and examples. 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?

Given two simple parameters, no output schema, and sibling tools, description covers purpose, usage, behavior, parameters, and examples completely.

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 100%, but description adds value by explaining scopes in more detail (e.g., 'one project + its tasks') and providing usage examples. Enhances understanding 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?

Clearly states it exports OmniFocus data as TaskPaper plain text with three scopes. Distinguishes from sibling tool import_taskpaper by explicitly saying not to use for import, and provides examples.

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 describes when to use each scope, gives examples, and warns against using for import, directing to alternative. Also notes safe to call repeatedly with no side effects.

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