Connect Notion show rundown

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

Annotations indicate readOnlyHint=false and destructiveHint=false, meaning it's a write operation but not destructive. The description adds no disclosure about side effects, whether it modifies an existing network, requires Notion credentials, or affects external services. It merely states the creation of a scaffold without describing behavioral traits beyond the annotation baseline.

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, focused sentence that front-loads the primary action and resource and then lists key components. Every word contributes meaning; there is no fluff or repetition of schema defaults.

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?

The tool has 10 parameters, no output schema, and sparse annotations. The description lists high-level components but omits crucial context: what the scaffold actually contains structurally, prerequisites (e.g., Notion access), how parameters relate to the scaffold, and expected result. This is insufficient for an agent to fully understand the tool's operation and effects.

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 only 20% (2 of 10 parameters described). The description mentions concepts like scene maps, property maps, and approval policy, which loosely map to scene_count, property_count, and approval_required, but it does not explain parameters such as database_id, adapter_mode, rundown_label, or adapter_url. The description only minimally compensates for the schema gaps and provides no detailed parameter semantics.

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's function: 'Create a Notion show-rundown scaffold' and lists specific included components (scene maps, property maps, approval policy, adapter source, token-safety notes). This is a specific verb+resource (Create + scaffold) and the Notion qualifier distinguishes it from the many generic create_ and scaffold_ tools.

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 usage scenario is implied by the name and description: use when you want to scaffold a Notion-based show rundown. However, no explicit guidance on when not to use it or which sibling alternative to prefer (e.g., scaffold_show) is provided. The context is not fully explicit but is inferable.

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