notion_create_meeting_notes

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

With no annotations, the description carries the full burden and does so well: it discloses async processing ('processing continues after this returns'), the required polling loop and terminal status, and the non-idempotency consequence ('calling it twice creates two sets of notes'). It also notes that Notion may rewrite the title during summarisation — exactly the surprises an agent needs warned about.

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 purpose and the polling contract, then a labelled parameter block. Every line carries information an agent would otherwise have to guess; nothing is padding.

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?

An output schema exists so return values needn't be explained, and the description still supplies the async lifecycle state to poll for, the source/parent-page coupling, and the non-idempotency caveat. Nothing essential for a correct call 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 0%, so the description must compensate, and it documents all five parameters: the four source prefixes with their semantics, parent_page_id's file-sources-only constraint, the language hint format and auto default, and summarize=False behaviour. This is meaning well beyond the bare types in the schema.

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?

Opens with a specific verb+resource+output: 'Create AI meeting notes (transcript + summary) from a recording.' That cleanly separates it from the read/query meeting-notes siblings, which merely retrieve notes.

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?

Explicitly routes the agent to notion_read_meeting_notes for polling and warns it is NOT idempotent, plus spells out which source form goes with or without parent_page_id. It stops short of contrasting with adjacent tools like notion_upload_file or notion_extract_file_text, so no explicit 'when not to use'.

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