vikunja_add_label_to_task

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

The description implies a mutation ('attach') but with no annotations, it fails to disclose idempotency, duplicate attachment behavior, error conditions, or permission requirements. The agent receives no safety or side-effect information beyond the basic action.

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 redundant information. It front-loads the verb and is immediately understandable.

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 a simple attach operation with two parameters, the description is minimal. It lacks usage guidelines, behavioral traits (e.g., idempotency, failure modes), and return-value expectations. This is especially critical since no output schema is provided.

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 already provides descriptions for task_id and label_id, covering 100% of parameters. The description adds the 'existing label' context, which clarifies that the label must already exist, but it does not explain ID formats or relationships 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 'Attach an existing label to a task' uses a specific verb ('attach') and clearly identifies the resource (label) and target (task). It distinguishes itself from sibling tools like vikunja_remove_label_from_task or vikunja_create_label.

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 such as creating a new label or removing a label. The description only states the action without any contextual prerequisites, exclusions, or mention of related operations.

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