wrike_get_attachment

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

No annotations are provided, so the description must carry the full burden of behavioral transparency. It merely states 'Get a specific attachment' without disclosing what the response contains, whether it returns metadata or file content, or any side effects. The ambiguity with sibling tools is not resolved.

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, 'Get a specific attachment by ID', which is appropriately sized for a simple one-parameter tool and front-loads the core action without any fluff.

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?

Despite the tool's simplicity, the description is incomplete given the sibling context. It does not clarify what 'get' returns compared to download_attachment or get_attachment_url, nor does it mention any prerequisites or output format. This ambiguity could lead to incorrect tool selection or invocation.

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 100% since the only parameter, attachmentId, is described as 'Attachment ID (required)'. The description adds no new semantic information beyond repeating 'by ID', so 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 'Get a specific attachment by ID' clearly identifies a get operation on an attachment resource, with a specific verb and resource. It distinguishes from sibling tools like download, preview, or URL by using 'get', though it does not explicitly state what representation is returned (e.g., metadata vs file).

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 like wrike_download_attachment, wrike_get_attachment_url, or wrike_get_attachment_preview. The description lacks any context or exclusions, leaving the agent to infer usage.

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