Connector: Notion act

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description's 'write action' wording is consistent with that. However, it adds no behavioral context beyond the annotations: it does not say which actions (delete, archive) are irreversible, what auth is needed, or what happens to existing content on update. Enumeration of the actions gives some severity signal, so a 3 is fair.

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?

A single front-loaded sentence with the verb and resource first and the action enumeration trailing. No filler or redundancy.

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?

A destructive multi-action write tool with a nested params object and no output schema needs more than one sentence. The description never explains what each action_type expects in 'params' or 'resource_id', leaving the agent guessing at per-action payload shape.

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 all three parameters are already documented, and the description merely repeats the action_type enum already in the schema. It adds no per-action parameter syntax or format guidance beyond the schema baseline.

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?

States a specific verb ('Execute a write action') and resource (Notion) and enumerates the action set, so the agent understands this is the mutation counterpart to connector_notion_search/fetch. The action list is clear but reads as generic cross-connector boilerplate (reply/label/send are dubious for Notion), which slightly blurs the true scope.

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 indication of when to use this versus connector_notion_search, connector_notion_fetch, or the same-named 'act' tools of other connectors. Nothing states prerequisites, which action_type maps to which intent, or that a search/fetch should precede a write.

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