notion_local_search

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

No annotations are provided, so the description carries full burden. It discloses 'from local cache' and performance traits ('Fast, offline, no API limits'), but does not mention potential staleness of cached data, whether any side effects occur, or how completeness is guaranteed. Search is read-only by implication, but that is not explicitly stated.

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 description is two sentences, front-loaded with the key directive 'PREFERRED for searching Notion.' Every phrase adds useful context (source, speed, offline capability, alternative guidance). No wasted words.

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?

Given the tool's simplicity (1 required param, no output schema), the description covers the core purpose, usage context, and key behavioral traits. It lacks an explanation of return value format or staleness caveats, but remains sufficiently complete for an agent to select and invoke the tool effectively.

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% for all three parameters, so baseline is 3. The description reinforces the 'type' parameter by mentioning 'pages and blocks,' but adds no additional meaning beyond what the schema already provides for 'query' and 'limit.'

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?

The description clearly states a specific verb (search) and resource (Notion pages and blocks from local cache). It also distinguishes itself from both the Notion API and sibling local tools by being 'PREFERRED for searching Notion.'

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?

Usage guidance is explicit: 'Use this instead of Notion API for all search operations' and 'PREFERRED for searching Notion.' This gives clear direction on when to choose this tool over alternatives.

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