taiga_task_custom_attributes_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 disclosure. It only states the action without mentioning required permissions, side effects on existing tasks, duplicate handling, or the response shape. The agent has no information about what happens after creation.

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 concise sentence with no filler. It is front-loaded and easy to parse, though it could benefit from a bit more structural detail about parameters or usage.

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 simple create operation, but the lack of annotations, output schema, and usage guidance leaves the agent without critical context such as permissions, return values, and how this relates to custom attribute values. The one-line description is not complete enough for reliable invocation.

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 description adds no parameter-level meaning. The schema provides descriptions for 'name', 'type', and 'project' (60% coverage), but parameters 'order' and 'description' are undocumented in both the schema and the description. The tool description does not compensate for this gap.

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 clearly identifies the resource as a 'custom attribute definition for task'. It distinguishes this tool from sibling operations like update/delete/list on task custom attributes and similar create tools for epics, user stories, and issues.

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 usage guidance is provided. The description does not state when to use this tool versus related endpoints, does not mention prerequisites such as project membership or permissions, and does not clarify that custom attribute values are managed through separate value endpoints.

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