notion_search_intelligent

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

No annotations are provided, so the description carries the full burden. It mentions routing under JWT/tenant/company scope but does not disclose behavioral traits such as read-only nature, side effects, error conditions, or performance characteristics. This is a significant gap for a search tool.

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 concise with 3 short lines plus Args. It front-loads the main action and routing. However, the body could be more informative without becoming verbose. It earns its place but lacks depth.

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?

Given the tool has 2 optional parameters, no annotations, and an output schema, the description fails to cover key aspects: what the tool actually searches, constraints on inputs, expected output (though output schema exists), and when to use it. The routing detail is useful but not sufficient.

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 input schema has 0% description coverage, but the description's Args section provides basic meaning: 'message' is a free-text objective, 'inputs' is an optional JSON string. This adds some value, but the descriptions are still vague (e.g., what kind of structured inputs are expected?). Compensates minimally for the schema gap.

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 states it runs the 'search_intelligent' action, but does not elaborate on what this action does (e.g., intelligently search Notion pages, databases, etc.). The name is self-explanatory, but the description adds little specificity. It fails to differentiate from sibling tools like notion_search or notion_search_by_title.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, contexts, or exclusions. Without this, an agent cannot know if this is the appropriate search tool for a given scenario.

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