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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description goes further by disclosing the return shape (verbatim content per artifact type), that files include download urls, and the notable quirk that an infographic or first slide returns as an image rather than text — genuinely useful behavior an agent cannot infer from the schema.

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?

Dense but front-loaded: the core read action and its payloads come first, followed by the slide caveat and endpoint. Every clause carries information, though the long enumeration of artifact types borders on list-like density.

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 largely discharges it by enumerating payload types and noting the image-return edge case. It stops short of covering error/empty-artifact behavior or response sizing, but an agent has enough to call it correctly.

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 description coverage is 100% and the single 'artifact' parameter is fully documented in the schema (id, sourced from notebook_list_artifacts or a job result). The description adds no syntax, format, or id-resolution detail beyond that, so the baseline of 3 applies.

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 (one artifact) and then enumerates exactly what content types come back (files with download urls, report text, quiz JSON, flashcards, mind map, table, slide texts, suggested items). It explicitly distinguishes itself from the sibling notebook_get_slide for accessing slides beyond the first.

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?

Names the alternative for a specific case: 'to see another slide use notebook_get_slide,' and the endpoint hint GET /artifacts/{artifact} clarifies scope. It does not address when to prefer notebook_get_source or notebook_get_note for overlapping content, so routing guidance is present but not exhaustive.

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