Import tasks

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

Discloses side effects (creates tasks by default, dryRun prevents writing) and format auto-detection. No contradictions with annotations; descriptions add value beyond minimal 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?

Four concise sentences, each adding distinct information: purpose, formats, auto-detection, dryRun. No wasted words, 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?

For a tool with 5 parameters and no output schema, description covers input formats, auto-detection, and dryRun. Missing edge cases (format detection failure) but overall adequate.

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?

Description adds meaning to content parameter (example formats) and explains format auto-detection and dryRun. Complements schema coverage (60%) by clarifying parameter usage beyond schema docs.

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 'Import a backlog from raw text into a board' with specific verb and resource, distinguishes from bulk add tools by specifying raw text formats (markdown, CSV, JSON) and auto-detection.

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?

Implies usage for bulk import from raw text; lists supported formats and explains dryRun for preview. Lacks explicit comparison to alternatives like add_feature or add_features_bulk, but context is clear.

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