backlog

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

With no annotations provided, description carries full disclosure burden. Critically reveals atomic batch behavior ('created atomically in a single batch') and return value ('Returns the count'), but omits error handling behavior (validation failures, partial success semantics) and side effects.

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?

Six sentences with zero waste. Front-loaded action ('Bulk-create'), followed by input constraints, behavioral traits, return value, and usage guidance. Every sentence earns its place with dense, actionable information.

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?

Thorough for a bulk import operation despite no output schema: describes return value (count), input validation rules (required description field), and atomicity. Minor gap on error behavior or limits, but sufficient for correct invocation.

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 has 100% description coverage with detailed field listings, establishing baseline 3. Description restates required vs optional fields but adds no syntax guidance, validation constraints, or format details beyond what the schema's example and description already provide.

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?

Excellent specificity with 'Bulk-create tasks from a JSON array' providing clear verb and resource. Explicitly distinguishes from sibling 'task_add' in final sentence, clarifying scope boundaries.

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?

Provides explicit dual guidance: 'Use this for migrating data or creating multiple tasks at once' states when to use, while 'For creating a single task interactively, use task_add instead' names the specific alternative, preventing tool selection errors.

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