task_parse_transport_text

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

No annotations exist, so description takes full burden. States 'Read-only; no side effects.' Mentions return warnings for unparseable dates, disclosing error handling. Behavior is fully transparent.

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?

Compact yet comprehensive, covering purpose, syntax, usage note, return fields, read-only note, and example with no superfluous content. Front-loaded with key points.

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?

Despite no output schema, description enumerates all return fields. Addresses input format, dependencies (tag_list), and side effects. Complete for a single-parameter parse tool.

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 with 100% coverage already describes 'text' parameter; description adds context about line-by-line parsing and project prefix syntax, enhancing meaning 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?

States clearly: 'Parse OmniFocus transport text DSL into structured task objects — no tasks are created.' Lists supported tokens and explicitly distinguishes from task creation, making purpose unambiguous.

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 advises not to use for creation and directs to pass returned tasks to task_create. Also instructs to resolve raw tag/project names with tag_list. Provides clear when-to-use and alternatives.

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