search

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

No annotations are provided, and the description only states that it searches content. It does not disclose any behavioral traits such as pagination behavior, rate limits, authentication needs, or what happens with partial matches. The presence of an output schema is not leveraged in the description.

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 a clean 'Args:' structure. It is front-loaded with the overall purpose and then lists parameters efficiently. No extraneous information.

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 output schema exists (but not shown), the description covers the essential aspects: what the tool does and all its parameters. It does not explain return behavior, but the output schema presumably covers that. Overall adequate for a search tool.

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. It explains each parameter: 'query: Text to search for', 'filter_type: Restrict results to "page", "database", or "" for both.', and 'max_results: Maximum number of results to return.' This adds significant meaning beyond the raw schema types and defaults.

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 clearly states 'Search Notion pages and/or databases.' It identifies the specific verb (Search) and resource (Notion pages and/or databases). Unlike sibling tools like search_pages (likely limited to pages) and query_database (targeted to a specific database), this tool covers both, providing clear differentiation.

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 lacks any guidance on when to use this tool versus alternatives like search_pages or query_database. No mention of context, prerequisites, or exclusions, leaving ambiguity for the agent.

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