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

Goes well beyond the annotations (readOnly/idempotent/non-destructive): documents sort order (oldest first by creation time and ID), page size default/max, cursor restart behavior after edits, that activityId caps at zero-or-one and cannot be combined with a cursor, and that the collection is live rather than a snapshot. This is exactly the extra behavioral context annotations cannot carry.

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?

The read purpose is front-loaded and every sentence carries information, with no filler. It is dense with semicolon-joined clauses, which slightly taxes scanning, but 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 an output schema present and annotations covering the safety profile, the description supplies everything else an agent needs: pagination contract, ordering, cursor lifecycle, and the activityId special case. Nothing required to call 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 coverage is 100%, so the baseline is 3, and the description earns above that by clarifying the limit default/max, the cursor's restart-after-edits semantics, and the activityId exact-match/no-cursor behavior. It adds real meaning beyond the field descriptions.

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 ('Read saved notes on this Site/Topic recommendation'), and the phrase 'without changing them' immediately separates it from the create/update/delete note siblings. An agent knows this is the read path for notes without opening any 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?

Gives a concrete when-to-use rule: 'Use this read after an uncertain write before retrying creation; creation may duplicate,' plus the activityId-vs-cursor choice. It does not name specific alternative tools or an explicit when-not-to-use, so it stops short of a full routing decision.

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