taiga_issues_create

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

With no annotations, the description carries the full burden of disclosing behavioral traits, but it merely restates the action 'Create a new issue.' It does not mention required permissions, side effects, error conditions, or any other behavioral context beyond the obvious write operation.

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 sentence with no extraneous content, making it efficient and front-loaded. However, it is perhaps too terse for a tool with many parameters, though it does not contain 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 the high complexity (14 parameters), no annotations, and no output schema, this one-sentence description is inadequate. It omits required fields, parameter semantics, and expected return behavior, making it difficult for an agent to invoke the tool correctly in non-trivial scenarios.

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 description coverage is only 14% (2 of 14 parameters have descriptions). The description does not compensate for the lack of parameter details, offering no explanation of fields like status, priority, or assigned_to. An agent must rely on the sparse schema without additional context.

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 uses the specific verb 'Create' and identifies the resource 'issue', which clearly distinguishes it from update/get/delete tools in the sibling list. However, it does not explicitly differentiate from taiga_issues_bulk_create, though 'new issue' implies a single issue.

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?

No guidance is provided on when to use this tool versus alternatives like taiga_issues_bulk_create or other create tools. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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