Create Semantic Page

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only mentions 'Create' and 'AFFiNE-native', but fails to specify mutation behavior, authentication needs, side effects (e.g., workspace membership validation), or what happens on failure. This is insufficient for an AI agent to safely invoke the tool.

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 a single, front-loaded sentence that efficiently conveys the core action. It avoids fluff but could be slightly more structured (e.g., listing key parameters or behaviors). Still, it earns its place with no wasted words.

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 has 5 parameters, no output schema, and no annotations, the description is too minimal. It does not explain expected return values, error conditions, or behavior when optional parameters are omitted. For a relatively complex tool, this leaves significant gaps in the agent's understanding.

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 80% (4 of 5 parameters have descriptions), so the schema already explains parameter meaning well. The description adds only a high-level purpose ('intentional section structure') without providing additional semantic context beyond what the schema offers. Baseline score of 3 is appropriate.

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 the action ('Create'), the resource ('AFFiNE-native page'), and the manner ('with intentional section structure and native block composition'). It effectively distinguishes this tool from siblings like 'create_doc' or 'create_doc_from_markdown' by emphasizing structured, semantic page creation.

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 implies usage for creating structured pages but does not explicitly state when to choose this tool over alternatives (e.g., 'create_doc' for simple pages, 'append_block' for adding content to existing pages). No when-not or when-to-use guidance is provided, leaving the agent to infer context.

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