notion_local_recent

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

Without annotations, the description carries the burden. It discloses useful behavioral traits: uses local cache, is fast, offline, and avoids API limits. This goes beyond the basic operation, though it could mention return format or cache staleness, but overall it adds meaningful context.

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?

Four short sentences that are mostly efficient, but there is redundancy between the first and last sentences both referring to browsing recent documents. Still, it is concise and front-loaded with key info.

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 simple tool (two optional numeric params, no output schema, no annotations), the description covers the essentials: what it does, when to use it, and its operational characteristics. It is complete enough for an agent to select and invoke it correctly, though it lacks explicit return format details.

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 baseline is 3. The description doesn't add extra parameter semantics beyond connecting 'recently modified' to the 'days' parameter, but the schema already explains both parameters clearly.

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?

Clearly identifies the tool as the preferred way to list recent Notion pages, with focus on recently modified pages from local cache. The description distinguishes it from siblings by emphasizing 'recent' and 'local cache', and directly positions it against the Notion API.

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?

Explicitly states when to use this tool ('for browsing recent documents') and gives a clear alternative ('Use this instead of Notion API'). The 'PREFERRED' label reinforces the recommendation, providing solid usage guidance.

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