taiga_userstories_attachment_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 of behavioral disclosure. The description only says 'Get a specific user story attachment' with no mention of error behavior, required permissions, return format, or side effects. This is a significant gap for a fetch operation with no annotation support.

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 short sentence, which is front-loaded and free of unnecessary words. However, it is so minimal that it adds little information beyond the tool name, making it under-specified rather than effectively concise.

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 simple with one parameter and no output schema, but the description provides almost no contextual information. It does not mention what the attachment represents, what response to expect, or any limitations. Given the lack of annotations and output schema, the description is incomplete for an agent to use confidently.

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 input schema has one parameter, id, described as 'Attachment ID,' providing 100% schema coverage. The description adds no extra meaning beyond the schema, so it relies entirely on structured data. With full schema coverage, the baseline of 3 is appropriate.

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 the action ('Get') and the resource ('a specific user story attachment'), which distinguishes it from sibling attachment_get tools for other object types such as epics, tasks, or issues. It is a specific verb+resource pairing, though it lacks additional scope detail that could make it completely unambiguous.

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. With sibling tools like taiga_epics_attachment_get, taiga_tasks_attachment_get, and taiga_issues_attachment_get, the description would benefit from explicitly stating that this is for user story attachments only. The resource type is implied by the name, but usage context or exclusions are absent.

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