dataprobe_get_ask_result

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

No annotations are provided, so the description carries the full burden. It only says 'Get', implying a read operation, but fails to describe behavior on invalid or nonexistent query ids, whether results are immediately available or may require polling, or any error handling. The description is too sparse for a tool with zero annotation support.

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, front-loaded sentence with no redundant content. Every word contributes to the core meaning, making it efficient and easy to parse.

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 one-parameter retrieval tool, the description is adequate but incomplete. It fails to explain the prerequisite that a query_id must first be obtained from dataprobe_ask, and with no output schema, it does not hint at what the returned result contains. The description covers the basic action but lacks integration 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?

The description mentions 'by query id', which provides context that the parameter identifies the ask result, but it does not explain where the id comes from (e.g., from a dataprobe_ask response) or its expected format. With schema coverage at 0%, the description adds minimal value beyond the parameter name itself.

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 ('Get') and identifies the resource ('DataProbe ask result') and the key qualifier ('by query id'). This clearly distinguishes it from sibling tools like dataprobe_ask (submission) and dataprobe_query_sql (SQL query).

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 phrase 'by query id' implies the tool should be used after an ask is submitted via dataprobe_ask, but this prerequisite is not explicitly stated. No alternative tools are mentioned, nor are any exclusions given. Basic context is present but not fully articulated.

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