taiga_tasks_attachment_get

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 says 'Get', implying a read operation, but does not disclose what is returned (e.g., metadata, content, URL), potential errors, or any authorization requirements. This is a minimal disclosure with no behavioral detail beyond the verb.

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 or redundancy. It communicates the core purpose efficiently.

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 very simple (one parameter, no output schema), and the description is minimally viable. However, with no annotations and no output schema, the description could add context about the return value or usage context. It is adequate but lacks depth—for example, it does not clarify whether the response is binary file content or attachment metadata.

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 documents the only parameter 'id' with description 'Attachment ID', so schema coverage is 100%. The description adds no additional meaning about the parameter, such as how to obtain the ID or whether it is a global ID or scoped to a task. Baseline of 3 is appropriate since the schema already covers the parameter fully.

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 a specific task attachment' clearly identifies the verb (get), the resource (task attachment), and specifies 'specific' to indicate retrieval by identifier. It distinguishes from sibling tools like taiga_tasks_attachments_list (list vs get) and other attachment_get tools for epics/userstories/issues through the word 'task'.

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 taiga_tasks_attachments_list or other attachment_get tools, nor does it mention any prerequisites or context (e.g., needing the attachment ID from a prior list call). It is a bare statement of what it does.

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