Search Notion

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds 'Risk: read' which is redundant. It does not disclose additional behavioral traits like whether it searches page titles only or full text, or if there is pagination or result limits.

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 very short (one sentence plus a note), which is concise. However, the 'Risk: read' note is unnecessary given annotations. Every word earns its place, but could be more informative without increasing length significantly.

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 a search tool with no output schema and minimal parameter descriptions, the description is insufficient for an agent to understand return behavior, search scope, or limitations. It lacks details on results structure, pagination, or query capabilities.

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 description coverage, the description adds minimal semantic value. It mentions 'matching a query' for the query parameter but does not explain its syntax, supported features, or the purpose of 'requestingAgent'. The schema provides constraints but no semantics.

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 it searches the connected Notion workspace for pages matching a query, which is a specific verb-resource combination that distinguishes it from sibling tools like notion_get_page (retrieve specific page) or notion_create_page (create new 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 does not provide explicit guidance on when to use or not use this tool versus alternatives. It only states 'Risk: read', which implies safe use, but lacks context such as 'Use this to find pages by keyword; use notion_get_page to retrieve full page content once found.'

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