get_async_task

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

Description adds 'poll' context, confirming repeated safe calls (consistent with idempotentHint, readOnlyHint). Does not contradict annotations. Does not disclose additional behaviors like rate limits or typical completion times.

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?

Extremely concise: 5 words in one sentence. No superfluous information. Front-loaded with core action and resource.

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?

Given low complexity (1 param, polling) and presence of output schema, description is sufficient. Covers status and result retrieval. Missing explicit mention of incomplete results if task not done, but 'poll' implies waiting.

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?

Single parameter task_id has 0% schema description coverage. Description does not explain the parameter's purpose, format, or where to obtain it, failing to compensate for the lack of schema documentation.

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?

Description clearly states the tool polls a background task's status and result. Uses specific verb 'poll' and resource 'task', distinguishing it from sibling tools like submit_async_task, cancel_async_task, and list_async_tasks.

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?

Description implies usage after submitting a task, but does not explicitly state when to use this vs alternatives (e.g., list_async_tasks, cancel_async_task). No guidance on prerequisites or context.

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