notion_list_databases

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool routes through an API under JWT scope, which is generic. It does not mention side effects, rate limits, pagination, or what happens when called (e.g., whether it lists all databases or requires filters). The minimal information is insufficient for safe usage.

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 very short (3 lines) and has a clear structure (intro, routing, args). However, it is too concise, omitting essential details like return type or usage notes. Conciseness is achieved at the expense of completeness.

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 (not described) and only one parameter, the description fails to explain the tool's output, the meaning of 'arguments', or how the tool interacts with Notion. For a tool with 0% schema coverage and no annotations, this is severely under-specified. The description does not enable an agent to use the tool correctly without additional context.

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 schema has 0% description coverage, and the description only says the single parameter `arguments` is a 'JSON string of arguments for the connector operation'. This adds vague context but does not specify what keys or values are expected. The agent cannot infer valid argument structure from this.

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 explicitly states it's a 'Notion connector operation `list_databases`', and the name strongly indicates listing databases in Notion. However, it does not differentiate this tool from sibling tools like `notion_query_database` or `notion_search`, and doesn't describe what exactly a 'database' is in Notion context. The mention of platform tool identifier adds 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?

No guidance is provided on when to use this tool versus alternatives such as `notion_query_database` or `notion_search`. There is no mention of prerequisites, limitations, or typical use cases. The description lacks any usage context.

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