notion_list_databases

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 reveals that databases are 'cached on this Mac', indicating local data retrieval rather than live fetch. However, it does not disclose read-only nature, authentication requirements, or potential staleness of cache.

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?

A single sentence that is front-loaded, concise, and contains no filler. Every word adds value.

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 parameters and no output schema, the description provides the essential purpose and return type (schema). However, it could be more complete by explaining the caching behavior more thoroughly (e.g., when it's updated) and what 'schema' includes in terms of structure.

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 tool has zero parameters, so schema coverage is 100%. With no parameters, the baseline score is 4 per guidelines. The description adds no param information, which is appropriate and unnecessary.

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 specific verb 'Lists' and resource 'Notion databases', and adds detail 'cached on this Mac with their schema (column names and types)'. It clearly distinguishes from sibling tools like notion_list_pages (lists pages) and notion_read_database (reads a database).

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 the tool is for listing databases and their schema, but does not provide explicit guidance on when to use this tool vs alternatives (e.g., notion_search, notion_read_database). No exclusions or when-not-to-use are given.

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