Create Data Source

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

The description states 'Add an additional Notion data source', implying a mutation, consistent with readOnlyHint=false. However, it does not disclose any additional behavioral traits such as required permissions, idempotency, or side effects beyond what annotations already imply. Since annotations are present, the description adds minimal extra transparency.

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 two sentences, front-loaded with the action, and no unnecessary words. Every sentence is essential.

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 (4 parameters with nested objects, no output schema), the description is minimal. It explains the basic purpose and exclusions but does not guide on how to structure parent or properties, which are required and have complex schemas. Adequate but leaves gaps.

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%, so baseline is 3. The description does not elaborate on parameter meanings beyond what the schema already provides, thus not adding significant value over the schema.

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 tool adds a data source to an existing database, and explicitly distinguishes from notion_create_database, which is used for creating new databases. The verb 'add' and resource 'data source' are 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 when-not-to-use guidance: 'Do not use this to create a new database; use notion_create_database for that.' This clearly differentiates from a sibling tool and indicates appropriate context.

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