Bulk Create Tasks

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Create Backlog issues'. It does not mention side effects on the temp files, idempotency, permissions, error behavior, or whether the operation can be undone.

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?

The description is a single front-loaded sentence with no filler. It leads with the action and object, then adds the source context, which is the most natural structure for this tool.

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?

The tool is a mutation with no annotations and no output schema, so the description should provide more behavioral context. It does not explain what 'temporary task files' are, whether files are modified or consumed, how the parent folders are resolved, or how this relates to sibling tools like list-task-files.

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?

The input schema is empty, so 0 parameters need documentation. Per the baseline for 0-parameter tools, the description does not need to add parameter semantics, and nothing is missing.

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?

The description states a clear action ('Create Backlog issues') and source ('local temporary task files in parent folders'), enough to identify the tool's primary purpose. However, it does not explicitly differentiate it from sibling tools like sync-issues or update-issues, leaving some potential ambiguity.

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?

The phrase 'from local temporary task files in parent folders' implies a particular workflow context, so an agent can infer roughly when to call it. There is no explicit guidance about when to prefer this tool over sibling tools or when not to use it.

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