notion_search

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

The description discloses search-by-title behavior, object type filtering, and last_edited_time sorting, which adds context beyond the tool name. With no annotations, it doesn't mention pagination, result limits, or whether search is full-text, but the core non-destructive search behavior is clear.

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?

Two short, front-loaded sentences convey the primary action, resource, and key options without redundancy. Every word earns its place.

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 simple search tool with no output schema, the description covers the essential operation and primary parameters. It omits workspace scope and return shape nuances, but the schema documents the extract parameter, reducing the need for description to explain response handling.

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 coverage is 100%, so baseline is 3. The description adds meaning by linking query to 'by title', explaining filter values (page/database), and clarifying the sort timestamp, which enriches the bare schema descriptions.

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/databases by title, which is a specific verb and resource. It does not explicitly differentiate from sibling notion_query_database, but the search scope over pages/databases is evident.

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 implies usage when you need to find pages or databases by title, and mentions filtering and sorting options. However, it gives no explicit guidance on when to prefer this tool over alternatives like notion_query_database or notion_retrieve_database.

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