get_bug_context

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

With no annotations provided, the description carries the behavioral burden, and it does disclose significant behavior: attachments are downloaded and returned inline, and no follow-up call is needed. It does not mention auth, rate limits, or error behavior, but for a read-focused tool the key operational trait is well communicated.

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 that front-loads the core purpose and packs the most important behavioral detail into the latter half without repeating information. It could be split into two sentences for readability, but there is no filler.

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 one-parameter read tool with no output schema, the description adequately conveys what the caller gets: details, comments, attachments, linked task, and inline image downloads. Minor gaps such as how non-image attachments are returned or error conditions do not undermine tool selection.

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 explain bug_id, its format, or where it comes from. The phrase 'for a bug' adds little beyond the schema's own field title 'Bug Id,' so the description fails to compensate for the low 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 states a specific action and resource: get full context for a bug. It also lists the included contents (details, comments, attachments, linked task) and adds a distinguishing detail (image attachments returned inline), making it clearly distinct from sibling context tools like get_task_context or get_project_context.

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 implies when to use this tool: when you need a bug's full context in one call, especially with visual attachments. However, it never explicitly names alternatives or states when not to use it, leaving the agent to infer the boundary from the sibling tool names and the word 'bug.'

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