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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' adds little, but the description goes further with result ordering ('newest first'), workspace scoping, and the exact response envelope. That return-shape disclosure is genuinely useful given there is no output schema.

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?

Three short sentences, front-loaded with what is listed and in what order, then filtering, then return shape. Efficient overall; 'Read-only' mildly duplicates the annotation and the parenthetical key names are slightly compressed but still clear.

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 no output schema, the description helpfully names the 'meeting_notes' key plus 'total' and 'has_more', so an agent knows how to paginate. The remaining gap is the undocumented 'limit' parameter, which matters for a paged list tool but is a single omission rather than a systemic one.

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 0%, so the description must carry parameter meaning: it does explain that 'query' matches over title and raw notes, which the bare schema does not. However, 'limit' is never mentioned at all — no default, no max, no effect on pagination — leaving half the parameters undocumented.

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 ... meeting notes') plus scope ('caller's', 'active workspace') and ordering ('newest first'), which an agent can act on directly. It does not, however, distinguish this from the sibling 'list_notes', leaving the meeting-notes-vs-notes boundary to inference.

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?

Implies usage for browsing the caller's notes with an optional narrowing filter, which is reasonable guidance. But it never says when to prefer 'get_meeting_note' or 'list_notes' instead, and gives no exclusion or prerequisite conditions.

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