taiga_epics_attachment_get

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

No annotations are present, so the description carries the full transparency burden. It only states 'Get', which implies a read-only operation, but does not mention authorization requirements, return format, or any effect on data. It adds little beyond the tool name.

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, front-loaded with the purpose, with no wasted words. It fits the expected format for a simple tool.

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 one-parameter getter, the description is minimally adequate. It clearly names the resource and the schema covers the parameter. However, it lacks any mention of response contents or prerequisites, and no output schema exists. It is not egregiously incomplete but could add a hint to use the list endpoint.

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 provides 100% coverage for the single 'id' parameter, described as 'Attachment ID'. The description adds 'epic attachment' context but does not explain param format or how to obtain the ID. Baseline 3 is appropriate because the schema already handles parameter semantics.

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 epic attachment' uses a specific verb and resource, clearly indicating it retrieves a single attachment by ID. It distinguishes from sibling list tools and other attachment getters by explicitly naming 'epic attachment'.

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 taiga_epics_attachments_list or attachment getters for other object types. The description implies usage when you have a specific attachment ID but does not state exclusions or alternatives.

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