get_task_context

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

With no annotations provided, the description carries the full burden. It discloses that image attachments are downloaded and returned inline, and that no follow-up call is needed, which is a valuable behavioral detail. It does not explicitly state that the operation is read-only or mention error cases, but the 'get' verb and the listing of returned content imply a safe read operation.

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 sentence but front-loads the core purpose ('Full context for a task in one call') before listing the components and the inline-image behavior. It is efficient and not overly verbose, though slightly long; it earns a solid 4.

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 description explains what the tool returns in detail (details, comments, subtasks, status history, attachments) and the inline image behavior. Since there is no output schema, this is necessary and sufficient for an agent to understand the result. It does not mention potential payload size or error handling, but for a read-only context tool, the information is complete enough.

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 0%, and the description does not add any meaning beyond the schema's 'task_id' string. It neither explains the format, where to find the ID, nor any constraints. The purpose is inferable from the tool name, but the description fails to compensate for the low schema coverage.

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 verb 'get' and the resource 'task context', and enumerates exactly what is included: details, comments, subtasks, status history, attachments, and inline images. It distinguishes itself from sibling context tools by emphasizing 'full context in one call' and the inline image behavior, making it unambiguous which tool to use for a 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?

The description says 'full context for a task in one call' and 'no follow-up call needed', which gives clear context that this is the comprehensive task-specific tool. It does not explicitly name alternatives (e.g., get_project_context, get_bug_context) or state when not to use them, but the scope is clearly task-focused, so the guidance is adequate.

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