notion_query_database

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

No annotations exist, so the description must fully disclose behavior. It does not state that the tool is read-only, lacks mention of side effects, permissions, rate limits, or pagination. The description is insufficient for an agent to understand the tool's behavioral impact.

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 relatively concise with two paragraphs, but the page_size parameter has no actual description (just a colon and newline). This incompleteness reduces clarity. Structure is acceptable but not exemplary.

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?

Despite having an output schema, the description fails to mention that the tool is read-only, contradicts the schema by marking database_id as required when it is optional, and omits information about pagination or response format. For a query tool with 4 parameters, this is incomplete.

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 0%, so the description must compensate. It adds basic meaning (e.g., 'Notion filter object as a JSON string') but lacks detail on expected JSON structures and does not clarify that database_id is optional (schema allows null, but description says 'required'). The truncated page_size description is also unhelpful.

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 rows in a Notion database with filters and sorts. It uses a specific verb ('query') and identifies the resource ('rows in a Notion database'), distinguishing it from sibling tools like notion_search which search across pages.

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?

No guidance is provided on when to use this tool versus alternatives like notion_query_data or notion_search. The description lists parameters but offers no context on when filtering/sorting is appropriate or prerequisites.

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