notion_read_meeting_notes

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

With no annotations, the description carries the full burden. It does disclose the key behavioral constraint—only ONE section is returned per call, with 'summary' as the default—which an agent needs for planning. It says nothing about permissions, whether the block must already exist, or behavior for an invalid section value, so gaps remain.

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 purpose sentence is front-loaded and the parameter notes are terse, each earning its place. The layout is a bit ragged (line-broken parameter list) 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?

For a 2-parameter read tool with an output schema present, the description covers purpose, the single-section constraint, and both parameters adequately. Only minor residual gaps (invalid-section behavior, whether block_id must be a meeting-notes block specifically) keep it from a 5.

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 compensate, and it largely does: it enumerates the valid section values ('summary', 'notes', 'transcript'), gives the default, and explains where block_id comes from. Enum values are not declared in the schema, so this is real added meaning.

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: reads one section of an AI meeting notes block. This distinguishes it from notion_query_meeting_notes (query) and notion_read_page (full page). It stops short of explicitly contrasting with notion_read_page or notion_read_page_markdown, which an agent could plausibly confuse it with.

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?

Useful routing is implied by the block_id provenance note (from notion_query_meeting_notes or a '[Meeting notes: …]' line in notion_read_page output), which tells the agent when this is the right follow-up call. However, there is no explicit when-not guidance or statement of how this differs from reading the page directly.

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