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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are ordered by date descending, pagination is supported, and filtering is optional, which helps an agent reason about result shape and iteration.

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 short sentences with zero filler; the core behavior (list recent notes, date descending) is front-loaded and the secondary capabilities follow. Every clause earns its place.

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 a full output schema, 100% parameter coverage and annotations covering safety, the description needs only to frame the operation, which it does. It could go one step further by clarifying scope (e.g., current user only, how far back 'recent' reaches), but nothing essential is missing for correct invocation.

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 limit, offset and note_type are already fully documented including enum meanings. The description only restates that pagination and note-type filtering exist, adding no syntax or constraint detail beyond the schema, making the baseline 3 correct.

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 ('List the user's recent notes and recordings') plus the ordering ('sorted by date descending'), so the agent knows exactly what comes back. It does not name or differentiate itself from siblings like search_notes or get_notes_by_label, which is the only thing keeping it from a 5.

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?

The 'recent notes' framing implies an exploratory, no-query browse use case, and it notes that filtering by note type is optional. However, it never says when to prefer this over search_notes or get_notes_by_label, nor any prerequisites, so usage is only implied rather than stated.

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