format_research_for_notion

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

With no annotations provided, the description carries the full transparency burden. It clearly discloses that this tool returns Notion API block content and does not create the page itself, as indicated by the workflow step 'First create a page... Then call this tool to get the formatted blocks.' It could further specify the types of blocks generated, but the core behavior is transparent and not misleading.

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 concise and well-structured with a front-loaded purpose and a numbered workflow that is easy to follow. The adjectives 'beautiful,' 'rich,' and 'stunning' add little functional value, but the overall description remains focused and 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 tool's complexity (9 parameters, no output schema, no annotations), the description explains the essential external integration context: how to wire this tool with page creation and block patching. It does not enumerate output block types, but the statement that it returns an exact Notion API block structure is sufficient for a caller to understand the return value and pass it downstream.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3 even though the tool description adds no per-parameter information. The workflow implicitly ties parameters to producing a research report, but no additional meaning is provided beyond the schema.

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 starts with a specific verb ('Generate') and resource ('Notion page content blocks for a market research report'), and clarifies the exact output type ('the exact Notion API block structure'). It clearly distinguishes itself from sibling formatting tools like format_watchlist_entry by focusing on research report pages rather than watchlist entries.

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 a clear three-step workflow involving API-post-page and API-patch-block-children, showing exactly where this tool fits in the broader process. It doesn't explicitly contrast this with alternatives like format_watchlist_entry or mention when NOT to use it, but the research-report focus and integration steps give strong contextual guidance.

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