Search Notion

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

Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds useful scope context ('shared with the Notion integration') but does not disclose pagination, sorting, or result behavior. This meets the lower bar expected when annotations are present.

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, front-loaded sentence with no filler. Every word contributes to communicating the core action and scope, making it appropriately concise.

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 5 optional parameters and an output schema, the description provides only a high-level object scope. It omits guidance on how to leverage query, pagination, or sorting, making it incomplete for an agent to invoke the tool effectively in varied scenarios.

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 for parameter explanations. It only hints at the 'object' parameter via 'pages or data sources' and ignores query, pageSize, startCursor, and sortDirection, leaving the agent without adequate parameter-level guidance.

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?

Description uses active verb 'Search' and specifies resource 'pages or data sources shared with the Notion integration.' It clearly differentiates from sibling tools like get_page/get_database by indicating a cross-resource search operation, though it doesn't explicitly contrast with query_data_source.

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 usage by stating what is searched, but it provides no explicit when-to-use guidance, no exclusions, and no mention of alternative tools. It is not misleading, just minimal.

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