queryNotionDatabase

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

No annotations are present, so the description carries the full burden. 'Retrieves and filters' clearly indicates a read-only operation, which is a key behavioral trait. However, it does not disclose other aspects like pagination behavior, authentication requirements, or how filters are processed. For a read tool, the core safety message is conveyed, but depth is limited.

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 concise sentence with no fluff or redundancy. It front-loads the core action and resource, making it immediately scannable.

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?

The tool has 4 well-documented parameters and no output schema, so the description does not need to explain return values. However, it lacks explicit guidance on when to prefer this over sibling tools (e.g., searchNotion for global search, listNotionPages for listing pages). The description is adequate for a simple query tool but not comprehensive.

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% (all parameters have descriptions), so the baseline is 3. The description merely summarizes the tool's overall function and does not add extra meaning to individual parameters beyond what the schema already 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 uses specific verbs 'Retrieves and filters' with a clear resource ('items from a specified Notion database'), making its purpose unambiguous. It distinguishes itself from siblings like listNotionPages (lists pages) and readNotionPage (reads a single page) by focusing on database-level queries with filtering.

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 clear usage context: when you need to query a Notion database with filtering and sorting. However, it does not explicitly name alternatives or state when not to use this tool, even though siblings like searchNotion and listNotionDatabases exist. This provides context but lacks explicit exclusions.

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