taiga_userstory_custom_attributes_update

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

No annotations are provided, so the description carries the full burden. It only says 'Update a custom attribute definition' without disclosing mutation behavior, partial vs full update, permission requirements, or effects on existing data. This is insufficient for a mutation tool.

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, clear sentence with no unnecessary words, making it concise and front-loaded. However, it could be slightly more informative without becoming verbose.

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?

With 5 parameters, no output schema, and no annotations, the tool requires more context. The description fails to mention that only 'id' is required, that other fields are optional, that the tool returns the updated definition, or how it differs from updating custom attribute values. This is a significant gap.

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 only 20% (only 'id' is described). The description does not explain that 'name', 'type', 'order', and 'description' are updatable fields or how they relate to the custom attribute definition. It adds minimal 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 clearly states a specific action ('Update') on a specific resource ('custom attribute definition for userstory'), which distinguishes it from sibling tools like create, delete, get, and from custom attribute updates for other entities (epic, task, issue).

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 implies usage when updating an existing userstory custom attribute definition, but lacks explicit guidance on when not to use it (e.g., for updating attribute values, which have separate tools like taiga_userstory_custom_attributes_values_update). No alternatives are mentioned.

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