notion-query

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal that results are 'summarized properties' and that filters/sorting are supported, but it doesn't disclose pagination behavior, rate limits, authentication expectations, or error handling. The word 'Query' implies read-only but not explicitly.

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 two sentences with no filler. It front-loads the core action and resource, then adds the return behavior. Every word earns its place.

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?

For a tool with five parameters, no output schema, and no annotations, the description is adequate but not fully complete. It covers the central behavior but omits operational details like pagination, result structure, and filter object construction. The schema helps by documenting parameters and linking to Notion's filter docs.

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%, as all five parameters have descriptions in the input schema, so the baseline is 3. The description adds the conceptual context of filters and sorting but does not provide parameter-level details beyond what the schema already contains.

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 a specific verb and resource: 'Query a Notion database with filters and sorting.' It also states the return value as 'matching pages with summarized properties,' which helps distinguish from siblings like notion-read. However, it doesn't explicitly contrast with those siblings.

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 tool is for querying Notion databases, but there is no explicit guidance on when to use it versus notion-read or notion-write. It doesn't provide exclusions or mention alternatives, 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.