Get Task Result

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

Annotations already set idempotentHint and readOnlyHint. The description adds value by stating it returns error/notFound for incomplete/unknown tasks and explicitly says it is idempotent and does not consume the task.

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, front-loaded with essential purpose, and each sentence adds distinct information without redundancy or wasted words.

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 the presence of an output schema, the description adequately covers the core behavior and error cases. It could mention the output schema exists, but this is minor. Annotations provide safety context.

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?

With schema description coverage at 0%, the description does not explain the taskId parameter at all. The only parameter is not described in text, leaving the agent to infer its meaning from the schema alone.

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 'returns' and resource 'final structured result for a completed task'. It differentiates behavior from not-yet-done tasks by specifying error returns. This distinguishes it from sibling tools like poll_task_status or list_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?

The description implies usage for completed tasks but does not explicitly guide when to use this over alternatives like poll_task_status or list_tasks. No mention of prerequisites or when not to use.

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