taiga_userstory_custom_attributes_values_get

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a safe read operation, the description adds no context about return shape, permissions, or behavior when the userstory is not found. It offers no more than the tool name already conveys.

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. It is well-structured and 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 getter with one parameter and no output schema, this is minimally adequate. It states the core action but omits usage context, return value details, and any differentiation from similar tools. The lack of annotations raises the need for more behavioral detail, making it only partially complete.

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 coverage is 100% – the id parameter is described as 'userstory ID'. The description's 'specific userstory' adds little beyond the schema. Baseline 3 is appropriate since the schema already documents the parameter.

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 'Get custom attribute values for a specific userstory' uses a specific verb ('Get') and resource ('custom attribute values' for a 'userstory'), clearly distinguishing it from sibling tools like taiga_userstory_custom_attributes_get (which gets the attribute definition) and the update/create variants.

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. It does not mention that this is for reading values as opposed to definitions, nor does it reference sibling tools for epics/tasks/issues that likely have analogous functions.

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