systemprompt_list_notion_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 describes the operation as a list function with sorting and return metadata, which implies a read-only, non-destructive action. However, it does not address potential limitations such as pagination, rate limits, authentication requirements, or error conditions, leaving gaps in behavioral 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?

The description is a single, well-structured sentence that efficiently conveys the tool's purpose, sorting, and return details without any redundant or extraneous information. It is front-loaded with the core action and appropriately sized for its complexity.

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 tool's low complexity (1 parameter, no output schema, no annotations), the description is mostly complete, covering purpose, sorting, and return metadata. However, it lacks details on behavioral aspects like pagination or error handling, which could be relevant for a list operation, preventing a perfect score.

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 input schema has 100% description coverage for its single parameter ('maxResults'), so the baseline is 3. The description adds value by specifying the sorting ('by last edited time') and return content ('key metadata including database title, schema, and last edited timestamp'), which are not covered in the schema, elevating the score to 4.

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 clearly states the specific action ('Lists all accessible Notion databases'), resource ('Notion databases'), and scope ('in your workspace'), with additional details about sorting ('by last edited time') and return content ('key metadata including database title, schema, and last edited timestamp'). It distinguishes itself from sibling tools like 'systemprompt_list_notion_pages' by focusing on databases rather than pages.

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 usage for retrieving database metadata, but it does not explicitly state when to use this tool versus alternatives like 'systemprompt_search_notion_pages' or provide any exclusions. It lacks guidance on prerequisites or specific contexts where this tool is preferred, leaving usage inferred rather than clearly defined.

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