notion_search

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

No annotations are provided, so the description carries the full behavioral burden. 'Search' implies a read-only operation, but the description does not confirm safety, permissions, rate limits, result ordering, or pagination behavior. It adds almost no behavioral context beyond the verb itself.

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 a single front-loaded phrase with no filler. It is appropriately sized for a concise name, though its extreme brevity leaves no room for useful clarifying context.

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 five parameters, nested filter/sort objects, no output schema, and no annotations, the description is too sparse. The schema documents parameters, but the description omits usage guidance, behavioral traits, and result format, leaving notable gaps for an agent choosing between search and database-query siblings.

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%, so all five parameters already have descriptions. The tool description adds no additional meaning for query, filter, sort, page_size, or start_cursor. Baseline 3 is appropriate because the schema does the heavy lifting.

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 ('Search') and resources ('pages and databases'), so the core operation is clear. However, it does not differentiate from sibling tools like notion_query_database or notion_get_page, leaving the agent to infer when this workspace-wide search applies versus structured database queries.

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 gives no when-to-use guidance, prerequisites, or alternatives. It does not mention that this is workspace-wide search rather than a database query, nor does it point to notion_query_database for filtered database retrieval. An agent receives no routing context.

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