notion_search_by_title

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

No annotations are present, and the description does not disclose any behavioral traits such as read-only nature, rate limits, or side effects. The description only covers routing details, which are not relevant for behavior.

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 short (two sentences) but includes non-essential routing information that does not help the agent. It is front-loaded with the tool name but could be more concise by omitting routing details.

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?

Despite having an output schema, the description does not explain how to use the arguments parameter, what search criteria are supported, or how results are returned. For a search tool, this lack of context is a significant gap.

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 only parameter 'arguments' is described as a 'JSON string of arguments for the connector operation' with no further detail on its expected structure or valid fields. With 0% schema description coverage, the description fails to compensate and adds little meaning.

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 is a 'search_by_title' operation for Notion, implying search functionality by title. However, it lacks specificity on what the tool actually does (e.g., search pages, databases, etc.) and does not distinguish it from sibling tools like notion_search or notion_search_intelligent.

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?

No guidance is provided on when to use this tool versus other search or notion tools. There are no usage scenarios, prerequisites, or alternatives mentioned, leaving the agent to infer usage from the name alone.

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