notion_set_page_visual

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

With no annotations, the description carries the transparency burden. It discloses that images are 'uploaded and attached,' that emoji applies to icons only, that remove clears the visual entirely, and lists valid source schemes. This goes beyond the bare schema, though it does not explain failure modes or effects on existing visuals beyond removal.

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 well-structured with a short opening sentence and a clear bulleted list for the exactly-one-of options. Every sentence carries semantic weight; there is no padding 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?

For a six-parameter tool with no annotations and no schema descriptions, the description covers the core behavior, valid source schemes, target options, and removal semantics. It omits filename and alternative-tool guidance, but an output schema exists, so return values don't need to be spelled out.

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 descriptions are absent (0% coverage), so the description must compensate. It explains target, emoji, source, and remove in detail, but never mentions the filename parameter and leaves page_id implicit. Thus it provides substantial but incomplete parameter coverage.

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 opens with a crisp verb-resource statement: 'Set or remove a Notion page's icon or cover image.' It immediately tells the agent both the action and the target resource, and it is distinct from sibling tools that upload/replace files or update page content.

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 intended use is implied by the purpose statement ('set or remove icon/cover') and the operational note that exactly one of emoji, source, or remove must be supplied, but there is no explicit guidance on when to choose this tool over alternatives or any exclusions/when-not-to-use.

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