notion_kb_author

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false. The description adds that execution routes through a domain-agent dispatcher under JWT, tenant, and company scope, which is useful scoping context but doesn't describe the concrete side effects or output behavior beyond that.

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 and front-loaded with the key operation: running the specific domain agent action. The routing detail and parameter notes are brief and each sentence adds information without padding.

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 an output schema and lightweight parameters, so the core invocation is documented. However, the description never says what `kb_author` does, what inputs it might need, or when to choose it over the many related dispatch and Notion tools, leaving meaningful gaps for correct selection and invocation.

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 0%, so the description is the only source of parameter meaning. It does explain that `message` is the free-text objective and `inputs` is an optional JSON string, but it doesn't elaborate on what structured inputs the `kb_author` action accepts or what a well-formed objective looks like.

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 that this tool runs the Notion domain agent action `kb_author`, with a specific verb and resource. It doesn't explain what the `kb_author` action actually accomplishes, but the name and structure make the immediate purpose recognizable.

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?

No guidance is given about when to use this tool versus alternatives like `dispatch_domain_agent` or the many direct `notion_*` tools. The description says what it routes through but not when a caller should prefer it.

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