search_pages

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

With no annotations, the description carries the full burden. It usefully discloses the auto-pagination behavior of fetch_all (default True) and how has_more/next_cursor depend on fetch_all=False, which is real behavioral context. It omits auth/permission requirements and rate-limit behavior, which matter for a Notion workspace search.

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?

Purpose is front-loaded in a single line, and the Args/Returns structure is easy to scan with no filler. Slightly verbose in restating cursor/result fields, but each line is informative.

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 the Returns block is somewhat redundant, though it clarifies the fetch_all-dependent fields. For a 5-parameter search tool with 0% schema coverage and no annotations, the description covers parameters adequately but leaves scope (workspace-wide vs filtered) and permissions unstated.

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 does provide a one-line gloss for each of the five parameters, including the important fetch_all default and page_size max of 100. The glosses are terse but cover the semantics that would otherwise be missing from 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 gives a clear verb+resource ('Search Notion pages and databases'), which is more specific than the bare tool name. It does not distinguish itself from siblings like query_database, so an agent cannot tell from the text alone when to prefer this over structured database querying.

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?

There is no explicit when-to-use/when-not-to-use guidance and no named alternatives, despite several closely related siblings (query_database, get_page). The filter_type note ('page' or 'database') hints at scope but is a parameter explanation, not usage direction.

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