notion_create_data_source

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

No annotations are provided, and the description fails to disclose any behavioral traits such as side effects, required permissions, rate limits, or error handling. The agent has no insight into what happens when this tool is invoked beyond a vague 'connector operation'.

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 includes unnecessary technical details about routing and scope (e.g., 'Routes through /api/tools/invoke under your JWT...') that do not help the agent decide when or how to use the tool. It wastes space on operational context instead of focusing on functionality.

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 complexity of creating a data source in Notion, the description is severely lacking. It does not explain what a data source is, what arguments are expected, or what the output will be (despite an output schema existing). The agent cannot effectively use this tool based on the description alone.

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 a single 'arguments' parameter (string) with 0% description coverage. The description only says it is a 'JSON string of arguments for the connector operation,' adding no detail about expected structure, required fields, or examples. The description does not compensate for the lack of schema documentation.

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 tool name 'create_data_source' clearly indicates creating a data source in Notion, and the description identifies it as a Notion connector operation. However, it does not explain what a data source is or differentiate from sibling tools like 'notion_list_data_sources' or 'notion_query_data_source', leaving the agent with minimal context.

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 provides no guidance on when to use this tool versus alternatives. It only includes technical routing information (JWT, tenant, company scope) which is irrelevant for usage decisions. No when-to-use or when-not-to-use instructions are present.

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