notion_search_databases

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

Discloses the integration's access limitation ('only sees databases explicitly shared with it') and return content. No annotations exist, so the description carries the full burden; it gives useful context but doesn't mention rate limits or pagination.

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?

Three concise sentences with front-loaded purpose; the access-scope note is useful and not redundant.

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 simple tool and presence of an output schema, the description covers the key workflow and access limitation. Missing parameter details prevent a 5, but overall it's adequately complete.

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?

The description never explains the 'limit' parameter and only implies 'query' is a search term. With 0% schema description coverage, this is a significant gap; the agent cannot know how limit behaves or what query matches.

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?

Clearly states 'Search Notion for databases the integration has access to' with a specific verb and resource, and distinguishes from notion_search_pages by focusing on databases. It also lists the return content (titles, IDs, property schemas).

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?

Explicitly tells the agent to use the returned database ID with notion_query_database, notion_describe_database, or notion_create_page, providing a clear usage workflow. However, it doesn't explicitly contrast with notion_search_pages or state when not to use.

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