notion_list_databases

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

The description discloses that the data comes from a local cache ('cached on this Mac'), which is useful behavioral context beyond what annotations would provide (none present). However, it does not explain cache freshness, behavior when cache is empty, or potential side effects, leaving some gaps.

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 a single, clear sentence with no wasted words. It front-loads the key action and resource, and every part is informative.

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 no output schema, the description does not detail the return format or handle edge cases (e.g., no cached databases). It states 'with their schema' but lacks specifics on how the data is structured, which is moderately incomplete for a tool with no output schema.

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?

There are zero parameters, and the schema coverage is 100%, so the description need not add parameter details. Baseline 4 applies per instructions; the description succinctly covers the tool's action.

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 uses a specific verb 'Lists' and resource 'Notion databases cached on this Mac', clearly distinguishing it from siblings like 'notion_list_pages' (pages) and 'notion_read_database' (read a specific database's content). It also specifies the output includes schema, adding clarity.

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 implies use when you need to see available databases and their schemas, but it does not explicitly state when to use this tool versus alternatives (e.g., 'notion_list_pages' or 'notion_search'). No exclusion criteria or alternative recommendations are provided.

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