search_pages

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

With no annotations provided, the description carries the full burden. It adds the important constraint that search is limited to page titles, which is useful. However, it does not disclose other traits like read-only behavior, result format, pagination defaults, or whether archived pages are included.

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 sentence of six words, with no redundant fluff. It is front-loaded and every word contributes to meaning, achieving high conciseness.

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 (2 parameters, both well-described in schema) and lack of output schema, the description is mostly sufficient for an agent to select and invoke the tool correctly. It covers the core purpose, but lacks some depth like usage distinctions and detailed behavior, which prevents a perfect score.

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% because both query and page_size have descriptive text. The description does not add meaning beyond the schema; it merely restates that search is by title, matching the query parameter description. Thus, baseline 3 applies.

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's function: 'Search for Notion pages by title'. The verb 'search' combined with the resource 'Notion pages' and scope 'by title' is specific and distinguishes it from siblings like get_page (retrieve by ID) or create_page (mutate).

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 by title, but it does not explicitly mention when to use this tool versus alternatives such as get_page for fetching by ID. No exclusions or comparisons are given, so guidance is implied rather than explicit.

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