get_task_context

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

No annotations provided, so description carries full burden. It describes the scope (fetching multiple content types) and hints at caching via 'refresh' parameter, but lacks details on expected latency, required permissions, error handling, or what happens if the ticket doesn't exist.

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?

Two sentences: first sentence states purpose and what it provides, second sentence gives specific usage triggers. Every sentence adds value, no fluff, and front-loaded with key information.

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?

Lists the types of content it synthesizes (requirements, comments, docs, standards, etc.), which is useful but incomplete. There is no output schema, so the description should clarify the return format (e.g., structured summary vs. raw text) but does not. Also lacks details on error states or prerequisites.

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 coverage is 100% with both parameters described. The description does not add extra parameter-level details beyond the schema (task_id format, refresh behavior). Baseline score of 3 is appropriate as the description provides no additional 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 uses a specific verb 'fetches and synthesizes' and clearly identifies the resource (Jira ticket). It lists multiple content types (requirements, comments, transcripts, docs, etc.), distinguishing it from sibling tools like get_standards (only standards) or search_context (general search).

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?

Explicitly states when to use: 'when starting work on a Jira ticket' and provides concrete trigger phrases ('work on PROJ-123', 'start TICKET-456'). Advises to 'call this FIRST', giving strong context, though it does not explicitly list when not to use or directly contrast with siblings.

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