search_notion

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

No annotations provided; description explains that it searches all connected pages and that omitting the query returns all pages, but lacks disclosure of auth needs, rate limits, or side effects.

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 concise with two short paragraphs, front-loaded with the action, and every sentence adds value. The Args/Returns formatting is efficient.

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 output schema exists (so return details not needed) and 2 parameters, the description covers the core functionality well. Minor omission: no mention of pagination or error behavior, but sufficient for the tool's simplicity.

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?

With 0% schema coverage, the description fully explains the 'query' parameter (keyword, full list if omitted) and 'limit' (default 20, max 100), adding essential meaning beyond 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?

The description clearly states the tool searches pages in a Notion workspace using a keyword, distinguishing it from sibling tools like create_notion_page, list_notion_pages, and read_notion_page.

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 description explains that omitting the keyword retrieves all accessible pages, but does not explicitly compare with sibling tools like list_notion_pages or provide when-not-to-use guidance.

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