notion_list_data_sources

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

No annotations provided, and the description fails to disclose any behavioral traits. It omits whether the operation is read-only, destructive, requires authentication, or has rate limits. The routing information is technical but not behavioral.

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 short but wastes limited space on routing details (e.g., '/api/tools/invoke under your JWT') that are likely irrelevant for the agent's decision. It lacks a clear, helpful structure and does not earn its sentences.

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?

Although an output schema exists, the description does not reference it or describe what the tool returns. The tool has one parameter and no complexity, but even for a simple list operation, the description should specify the output format (e.g., list of data source IDs, names) to be complete.

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 sole parameter 'arguments' is described as 'JSON string of arguments for the connector operation,' which adds no meaningful detail beyond the schema's type. With 0% schema description coverage, the description should explain what valid JSON keys/values are expected, but it does not.

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?

Description merely restates the tool name 'list_data_sources' and adds routing details. It does not explain what a Notion data source is or how listing them differs from other notions operations like query_data_source or create_data_source. The purpose is vague and tautological.

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 on when to use this tool versus alternatives such as notion_query_data_source or notion_list_data_source_templates. No context on prerequisites, filtering, or limitations. The description gives zero usage direction.

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