query_database

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

With no annotations provided, the description must fully disclose behavior; it only lists supported features (filtering, sorting, pagination) without explaining pagination cursor handling, result size limits, or read-only semantics. It adds little beyond what the schema already reveals.

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?

A single sentence that communicates the core function efficiently with no filler. It is appropriately sized.

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 no output schema, so the description must explain return values and pagination behavior. It only says 'retrieve pages' without describing the response structure, next_cursor, or how page_size interacts. This is insufficient for a tool with nested objects and 5 parameters.

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 schema has 100% coverage with examples for filter and sorts. The description merely restates these features ('Supports filtering, sorting, and pagination') and provides no additional semantic context for the parameters.

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 precisely states 'Query a Notion database to retrieve pages matching filter criteria,' identifying the verb (query), resource (Notion database), and outcome (retrieve pages). This distinguishes it from sibling tools like get_page (single page) and search (workspace-wide 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 description implies the use case of retrieving filtered pages from a specific database but does not explicitly mention when to choose it over alternatives like search or get_database. No prerequisites or exclusions are stated.

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