notion_link_review

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions routing through the domain-agent dispatcher with JWT/tenant/company scope, but does not disclose side effects, destructive potential, idempotency, or any constraints. This is insufficient for an agent to understand what happens when the tool is invoked.

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 relatively short (three lines of prose plus the args list). However, the first two sentences are somewhat repetitive ('run the action' and 'routes through the dispatcher') and could be merged. It is adequate but not maximally efficient.

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 low complexity, the description is incomplete. It fails to explain what the 'link_review' action does, what outcome to expect, or that an output schema exists. An agent cannot determine when or why to use this tool without external knowledge.

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?

The description adds clear meaning to both parameters: 'message' is a free-text objective, 'inputs' is an optional JSON string for structured inputs. Since the schema itself has 0% description coverage (no parameter descriptions), this addition is valuable and helps the agent understand how to fill the parameters.

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 it runs the 'link_review' action on the Notion domain agent, but never explains what 'link_review' actually does in business terms. It is clear that it invokes a specific action, but the purpose is vague compared to sibling tools like notion_query_database or notion_create_page which have explicit purposes.

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 provided on when to use this tool versus other Notion tools or domain agent actions. The description only says it routes through the dispatcher, but does not mention use cases, prerequisites, or alternatives.

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