taiga_priorities_create

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

With no annotations provided, the description must carry the burden of disclosing side effects, permissions, or response behavior. It only says 'create', implying mutation, but gives no details about required project context, possible errors, or output. This is a significant gap for a 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 extremely short, but this is under-specification rather than conciseness. The sentence is grammatically awkward ('a new priorities') and provides almost no useful content, so it does not earn its place in a helpful way.

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 create operation with 5 parameters and no output schema, yet the description gives no context about priorities, project association, or typical usage. It is incomplete even for a simple CRUD tool, especially with no annotations to supplement it.

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 60%, meaning 'order' and 'is_closed' lack descriptions. The tool description adds no parameter explanations or guidance on how required parameters (project, name) interact. It fails to compensate for the undocumented parameters, providing no value beyond the schema.

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 'Create a new priorities' clearly states the verb (create) and resource (priorities), but it is essentially a restatement of the tool name. It lacks detail about what a priority is in Taiga or how this creation differs from other entity creation tools, making it vague and minimally informative.

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 use this tool versus alternatives, no prerequisites (e.g., project existence), and no mention of related tools like taiga_priorities_list or taiga_priorities_update. The description provides zero contextual instructions.

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