set_current_page

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

Fully discloses the tool is deprecated and blocked by the relay server. No annotations exist, but description alone provides complete behavioral context.

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?

Single, clear sentence that efficiently communicates deprecation, alternative, and related tool. Slightly verbose with 'DEPRECATED —' but overall well-structured.

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 is deprecated and should not be used, the description covers all necessary context: what it did, why it's unusable, and how to achieve the same effect. Complete for the intended use.

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 has 100% coverage for the single parameter (pageId). Description adds context that it's a node ID, but schema already describes it as 'ID of the page'. No additional semantics needed beyond baseline.

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?

Description explicitly states deprecation, the tool's original purpose (stateful command to set current page), and provides alternative method. It clearly differentiates itself from siblings by marking itself as unusable.

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 tells when not to use (deprecated and blocked) and what to use instead (pass page ID as parentId on creation commands). Provides a concrete alternative tool (get_pages for discovery).

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