notion_search

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

The description frames the tool as a pure read ('Search', 'returns nothing that has not been shared', 'lists everything visible'), while the annotations declare readOnlyHint=false, i.e. the call may modify state. This is the same conflict pattern as a 'create' description paired with readOnlyHint=true, so the text and structured metadata contradict each other.

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?

Three tight sentences, front-loaded with the verb and resource, then the two key constraints (titles only, shared-only), then the discovery behavior. No filler or repetition.

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?

Because the schema is fully documented and there is no output schema, the description need not explain parameters or return shape; it correctly focuses on scope and the search surface. It is nearly complete, though it says nothing about pagination limits or the read-only question raised by the annotations.

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%, so the schema already explains query, filter, pageSize, startCursor and sort. The description's 'With no query it lists everything visible' restates the query parameter's own schema text rather than adding syntax or format detail, so the baseline 3 applies.

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?

Specific verb+resource+scope: 'Search the titles of pages and data sources shared with this integration.' The clause 'Titles only — it does not search page content' pins the exact search surface, so an agent can distinguish it from content-oriented or data-source-querying siblings without opening the schema.

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?

Gives a concrete usage pattern: 'With no query it lists everything visible, which is how you find the IDs to start from' — an explicit discovery workflow. It does not name an alternative tool or state when NOT to use it, so it stops short of a 5.

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