notion_query_database

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

No annotations are present, so the description carries the full burden. It does disclose that the operation returns pages and supports pagination, but does not mention whether it is read-only, any side effects, permissions, or how pagination is performed. This is a minimal but accurate behavioral overview.

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 short sentences deliver the core message without fluff: querying with filters/sorts, returning pages, and pagination support. It is concise and front-loaded with the primary purpose.

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?

With no output schema and no annotations, the description correctly identifies the return type and key capability. Minor gaps exist around pagination mechanics and default extract behavior, but the schema covers the extract default, making the description complete enough for most agents.

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 input schema already describes all parameters, including the important extract default behavior and page_size max. Since schema_description_coverage is high, the baseline is 3, and the description itself adds no extra parameter-level meaning beyond what the schema provides.

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 'Queries database with filters/sorts' and that it 'Returns array of pages (results)', which distinguishes it from retrieving a database object or searching. It names the primary verb and resource, but does not explicitly differentiate from sibling tools like notion_retrieve_database or notion_search.

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 phrase 'Queries database with filters/sorts' implies the primary use case: querying a database to get matching pages. However, it does not provide explicit guidance on when to choose this over alternatives, nor any exclusions, so usage context is only implied.

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