taiga_userstories_create

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

With no annotations provided, the description carries the full burden of behavioral transparency. It only states that the tool creates a user story, but fails to disclose return values, side effects (e.g., creation of associated objects), permission requirements, or error behavior. For a mutation tool, this is a significant gap.

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, which is concise in length, but it is under-specified for a tool with 18 parameters. It provides no additional value beyond the tool name and does not earn its place. The brevity here is a symptom of incompleteness, not effective conciseness.

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 tool's high complexity (18 parameters, no annotations, no output schema), the description is completely inadequate. It does not explain required fields (project, subject), what the response contains, or any operational caveats. The agent would have little context to use this tool correctly.

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 schema description coverage is only 28% (5 of 18 parameters have descriptions), and the tool description mentions no parameters at all. It does not compensate for the low schema coverage, leaving the semantics of 13 parameters undocumented both in the schema and description. This is a serious deficiency.

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 clearly states the action ('Create a new user story') with a specific verb and resource. It does not explicitly differentiate from sibling create tools (e.g., taiga_tasks_create), but the resource type 'user story' is unambiguous. The statement is a near-tautology of the tool name but adds a human-readable phrasing.

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 description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as an existing project or required parameters. Usage is merely implied by the verb 'create', which is insufficient for an 18-parameter tool.

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