Create Data Source

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

Annotations indicate readOnlyHint=false and destructiveHint=false, which the description supports by stating 'add', implying mutation but not destruction. However, the description does not add behavioral context beyond what annotations provide, such as authentication requirements, error conditions, or effects on the database.

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 sentence that is concise and front-loaded with the key action. Every word is useful; no fluff. It efficiently conveys the purpose and exclusion.

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 complexity (4 parameters, nested objects, no output schema), the description covers the core distinction from sibling tools and relies on the schema for parameter details. It lacks return value info and prerequisites, but the action is straightforward enough that the description feels complete for agent use.

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?

Schema description coverage is 100% (all parameters have descriptions). The tool description does not add any parameter-specific information beyond the schema, which is detailed. The description's mention of 'existing database' aligns with the schema's 'parent' parameter description. Baseline 3 is appropriate.

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 action: 'Add an additional Notion data source to an existing database.' It explicitly distinguishes from creating a new database by referencing 'notion_create_database' as the alternative. The verb 'add' combined with the resource 'data source to an existing database' is specific.

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 explicit guidance on when to use this tool (adding a data source to an existing database) and when not to (creating a new database), naming the alternative tool. However, it does not mention other scenarios or alternatives for adding data source items or other related tools.

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