taiga_create_issue

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about permissions needed, defaults applied to unspecified fields, whether the created issue is returned, or the fact that project_id and subject are mandatory. It only implies the tool is a mutation by the word "Create".

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?

A single short sentence with no filler and the operation front-loaded, but its brevity comes at the cost of under-specification rather than efficiency. Nothing is wasted, but much is missing.

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 an 8-parameter mutation tool with no annotations and no output schema, the description is far too thin to let an agent call it correctly without opening and interpreting the raw schema. It should at minimum name the required fields and describe accepted values for the enumerated-looking fields.

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 0% across 8 parameters, and the description only name-drops three optional fields (type, priority, severity) without explaining accepted values, defaults, or formats. It never mentions the two required parameters, project_id and subject, nor tags, assigned_to, or description.

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 names a specific verb and resource ("Create an issue") and lists three of the fields it sets, so the core operation is unmistakable. It does not distinguish itself from siblings such as taiga_create_user_story or taiga_create_task beyond the word "issue", leaving the agent to rely on the tool name for that separation.

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?

There is no guidance on when to create an issue versus a user story, task, or epic, nor any mention of prerequisites like project membership or the required project_id. The agent must infer context entirely from the tool name.

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