notebook_query_status

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

Describes behavior well: returns result on completion or interim status, and suggests polling. However, without annotations, it doesn't explicitly state that the tool is read-only (non-destructive) or note any rate limits.

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?

Three concise sentences with no wasted words. The most critical information (purpose and polling advice) appears first.

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?

With an output schema present, the description doesn't need to detail return values. It fully covers what the tool does, how to use it (polling), and the termination conditions.

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?

Parameter 'query_id' is fully described in the schema (100% coverage). The description only restates that it comes from notebook_query_start, adding no new semantics 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 the tool checks the status of an async notebook query, differentiates from notebook_query_start (which starts the query), and specifies it returns the result when completed or the current status otherwise.

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?

Explicitly advises to poll every few seconds until status is 'completed' or 'error', giving clear when-to-use and polling frequency instructions.

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