get_chat_history

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

With no annotations, the description carries the full burden and does add real context beyond the schema: it states the RPC/no-browser execution model and discloses a significant platform constraint that only the most recent conversation is available unless conversation_id is supplied. It omits auth requirements and error behavior when no conversation exists, but covers the key behavioral surprises.

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, both earning their place: the primary action and ordering come first, followed by the execution model and the conversation-selection caveat. No filler or redundancy.

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?

Return values need not be explained since an output schema exists, and every parameter is documented in the schema. What remains is minor: no note on authentication state or behavior when a notebook has no history, but nothing critical to invoking the tool correctly is missing.

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%, so all four parameters are already documented. The description restates the conversation_id default behavior, adding little beyond the schema's "Defaults to the most recent one", so the baseline 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?

Specific verb and resource: "Read back the questions and answers already recorded in a notebook, newest first." The phrase "already recorded" implicitly separates it from notebook_ask (which creates new turns) and delete_chat_history (which removes them), though no sibling is named outright.

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?

Usage context is implied via "already recorded" and the newest-first reading order, and the note about only the most recent conversation being exposed helps frame retrieval expectations. However, no explicit when-to-use/when-not guidance or named alternative (e.g. delete_chat_history, note_save_chat) is given.

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