webextrator_get_task

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

No annotations are provided, so the description carries full burden. It states the tool returns task status and result data, and implies polling behavior. However, it does not disclose whether the task is deleted after retrieval or any other side effects. The description is adequate but not thorough.

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 very concise: three short sentences plus bullet-like use cases. It is front-loaded with the verb and resource. No 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?

The tool is simple, schema covers all parameters, and output schema exists (so return format is explained). The description is sufficient for basic usage. It could mention that no parameters are required, but that is implied by default values.

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 adds value by clarifying that task_id is obtained from an extract/render request and that trace_id is an alternative lookup. This enhances understanding beyond the schema.

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 it retrieves the result of a single previously created extract or render task. The verb 'Retrieve' and resource 'result of a single... task' are specific. It distinguishes from siblings like webextrator_get_tasks_batch which retrieves batch results.

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 provides two explicit 'Use this when' conditions: after submitting an extract/render request and getting a task_id, and when wanting to poll for a specific task by ID. This gives clear context, though it could explicitly mention alternatives like 'for batch retrieval, use webextrator_get_tasks_batch'.

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