notebook_query_start

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

Explains async behavior, immediate return of query_id, and need to poll for result. With no annotations provided, the description effectively covers the key behavioral traits. However, it could mention error handling or timeout behavior more explicitly.

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?

Concise and well-structured: first sentence states purpose, second gives usage condition, third explains workflow. No redundant sentences.

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 description covers the main asynchronous workflow and distinguishes from sibling, but could include more on error states, limitations, or details about the output schema. Still, it provides a solid understanding for an AI agent.

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% and parameter descriptions in the schema are already clear. The tool description adds little beyond restating the purpose of the tool; no additional semantic context for individual parameters.

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?

Description clearly states 'Start a notebook query asynchronously for large notebooks that may timeout.' and explicitly contrasts with sibling tool notebook_query, making the purpose and resource distinct.

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?

Provides explicit when-to-use guidance: 'Use this instead of notebook_query when querying notebooks with many sources (50+) where the response may take longer than 60 seconds.' Also describes the workflow, including polling.

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