athena_extraction_task

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

With no annotations, the description carries the full burden. The verb 'fetch' implies a read-only operation, and listing the components gives some clarity. However, it doesn't explicitly state that the tool has no side effects, or what happens if the task_id is invalid.

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, efficient sentence that immediately states the action and the key data returned. 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?

For a simple fetch-by-ID tool with one parameter, the description is reasonably complete. It states what is fetched and the included components, which covers the return value since no output schema exists. It lacks error-handling details, but that's not critical for such a simple read operation.

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 0%, so the description must compensate. It implies that task_id identifies which extraction task to fetch, but it doesn't explicitly describe the parameter's semantics beyond that. The description adds value by explaining what the task includes, which indirectly clarifies the purpose of the parameter.

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 tool fetches a specific resource (one extraction task) and lists its key components (seed, transform contract, status, result refs). It doesn't explicitly distinguish from sibling tools like athena_extraction_result, but the mention of 'result refs' hints at a different level of detail.

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 no guidance on when to use this tool versus alternatives. It doesn't mention any conditions, prerequisites, or the relationship to sibling tools such as athena_extraction_run or athena_extraction_result.

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