sb_page_open

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

While the readOnlyHint annotation declares safety, the description adds behavioral context by explaining the tool is a prerequisite for mutations and returns an outline. It does not explicitly state it is read-only, but the annotation covers that.

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 two concise sentences, front-loaded with the primary purpose and followed by clear usage instructions. No filler or redundant information.

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?

The description provides sufficient context for a straightforward tool: it explains when to call it and how to obtain identifiers. It does not detail return format or error cases, but these are not critical for an outline-returning read operation.

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 schema has no parameter descriptions, and the description only indirectly hints at page_id's purpose via the reference to finding page IDs. site_id is completely unexplained, leaving agents to infer its meaning.

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 (open a page for editing) and the return value (outline), and distinguishes it from sibling tools by specifying it should be called before mutation operations and referencing how to find page IDs.

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?

Explicitly states when to use the tool ('Call before any sb_add / sb_set / sb_move / sb_remove') and provides guidance on obtaining page IDs via sb_api_find.

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