notion_template_runner

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

The routing sentence adds legitimate context beyond the annotations: execution passes through the platform's domain-agent dispatcher and is scoped to the JWT/tenant/company, which is useful operational context. However, given destructiveHint=true, the description should at least hint at what the action modifies or destroys; it instead says nothing about side effects, so a significant disclosure gap remains.

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 compact — two prose sentences plus a two-line args list — and front-loads the action before context. The args section is scannable and earns its place given the empty schema descriptions, though the routing sentence is mildly boilerplate.

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?

For an opaque generic executor with 0% schema coverage and a destructive annotation, the description is far from complete: an agent cannot know what template_runner does, what outcome to expect, what inputs to provide, or when to prefer it over dispatch_domain_agent or the direct notion_* siblings. The existence of an output schema helps only marginally since the input contract is undocumented.

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?

With 0% schema coverage, the description carries the burden, and it does add meaning: message is labeled a 'free-text objective' and inputs an 'Optional JSON string of structured inputs.' It falls short of full compensation — it never says which JSON keys template_runner expects, how message and inputs interact, or whether message is effectively required despite having a default.

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 states a specific verb and resource ('Run the notion domain agent action template_runner') and explains the dispatch mechanism, so it is not a pure tautology. However, it largely restates the tool's own name — what running template_runner actually accomplishes (which templates it acts on, what it creates/modifies) is never defined, leaving the purpose genuinely vague.

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. With siblings like dispatch_domain_agent (which appears to offer the same dispatcher mechanism) and dozens of direct notion_* tools, nothing tells an agent why this wrapper should be chosen over them, what conditions select it, or when not to use it.

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