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

Beyond annotations it discloses that this is synchronous ("Not a job"), a ready-source precondition, and the return shape (note id + JSON tree). These are useful since sibling tools involve jobs. It doesn't discuss idempotency or cost, but annotations already cover the safety profile (readOnly/destructive/idempotent).

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 action, then precondition, then the alternative, then the endpoint. Every clause carries distinct information with no filler; two compact sentences do a lot of work.

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?

Although there is no output schema, the description explains the return value ({ name, children } JSON tree plus note id), the failure mode, and the routing alternative. Nothing needed to invoke it 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 the schema already documents all four parameters including the sources default. The description's "ready sources (or the ones given)" lightly reinforces the sources default but adds no syntax or format detail beyond the schema. 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+resource ("Generate a mind map of the notebook's ready sources... saved as a note") and distinguishes it from the similar-sounding notebook_generate_artifact/type mindmap sibling. An agent can tell exactly what it produces without opening a schema.

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 explicitly ("For Studio's interactive mind map artifact use notebook_generate_artifact with type mindmap instead") and states the precondition under which the call fails ("refused while no source is ready"). Both when-to-use and when-not are covered.

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