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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral detail: the ~50 s wait cap and the instruction to call again while the job is still running, which tells the agent this is a polling endpoint rather than a blocking one.

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?

Front-loaded with the core action and return payload, with the polling guidance and the GET path trailing. The parenthetical artifact enumeration is dense but informative; the sentence is long but nothing is redundant.

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 no output schema, the description carries the return-value burden and does so by listing status, artifact forms, and research results. It does not say what a failed/cancelled job returns or point at notebook_retry_artifact for that case, which is the remaining gap.

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%, so both parameters are already documented (baseline 3). The description goes beyond the schema by explaining the polling pattern implied by `wait` ('call again while it is still running'), which is operational meaning the schema's one-line hint does not convey.

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?

States a specific verb (read) and resource (a Studio or research job), then enumerates what comes back: status, artifacts with download URLs, text/structured content, images, or research results. This distinguishes it cleanly from notebook_list_jobs (plural, listing) and notebook_get_artifact (single artifact).

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?

'Use it for every jobid another tool hands back' gives an explicit trigger condition, and the wait guidance tells the agent how to poll. There is no explicit when-not or named alternative (e.g. list_jobs vs this), so it stops short of a 5.

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