Get Notebook

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that the response includes sections and section groups, which is useful beyond annotations. No behavioral surprises implied.

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?

Two sentences, each earning its place. The first states the core function, the second provides essential usage guidance. No extraneous text, front-loaded.

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 read-only tool with a single parameter and no output schema, the description sufficiently covers what the tool does and what it returns. It could slightly improve by distinguishing from get-notebook-hierarchy, but given other context signals, it is largely complete.

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?

With 100% schema coverage, the description adds value by explaining the purpose of notebookId and explicitly telling the agent to obtain it via list-notebooks. This goes beyond the schema description.

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 it retrieves detailed info about a specific notebook by ID, including sections and section groups. It distinguishes from siblings like get-notebook-hierarchy by implying a more comprehensive response, and provides a prerequisite (list-notebooks).

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 use list-notebooks first to obtain the notebook ID, providing clear usage context. However, it does not mention alternatives like get-notebook-hierarchy or when to use this over other sibling tools, so slightly below maximum.

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