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

Annotations already establish that this is a non-read-only, non-destructive, closed-world write, and the description adds that the result is a 'numbered figure' in the notebook. It does not say whether repeat calls duplicate figures, how numbering is assigned, or what happens when nothing is on the stage - gaps that matter for a writer.

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?

A single front-loaded sentence that defines the action and then spends its remaining words on the one genuinely ambiguous term ('drawing'). Nothing is wasted.

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 all six parameters optional, 100% schema coverage and an output schema present, the description only needs to explain the action and its target, which it does. The default-entry behavior and duplicate handling are left entirely to the schema.

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 tab, caption, drawing, entry_id and _subject are all documented in the schema itself. The description adds no parameter-level meaning beyond clarifying conceptually that the source is something on screen; 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?

States a specific verb and resource ('put a drawing ... into the lab notebook as a numbered figure') and disambiguates 'drawing' with a concrete enumeration (chart, gel, map, any picture a tool drew on the stage). It does not name or contrast any sibling, but the intent is unmistakable.

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 is only implied: the agent must infer that this follows a tool that drew something on the stage. There is no explicit when-to-use or when-not statement, and no routing to alternatives such as notebook_cross_refs or record_experiment.

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