convert_page

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether the conversion is reversible, what happens to the page's content, tags, or links after conversion, or whether any permissions are required. 'Returns: Serializable conversion confirmation' is too vague to count as meaningful behavioral disclosure.

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 short and front-loads the core purpose, with parameter notes in a compact Args block. The 'Returns' line adding little beyond the output schema is the only mild padding.

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?

An output schema exists, so return values need not be described, and the parameters are well covered. What is missing for a mutating operation with zero annotations is the behavioral side: reversibility, side effects on page content and links, and when conversion is the right choice versus move_page or copy_page.

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 0%, yet the description documents all three parameters: target_kind with its two allowed values, path as a slash-separated page path, and id as the preferred selector when both selectors are supplied. The id-over-path precedence rule is a genuinely useful detail not derivable from 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?

States a specific verb and bidirectional resource transformation ('Convert a page to a section or a section to a page'), which is unambiguous about what the tool does. It does not, however, distinguish itself from adjacent siblings like move_page, copy_page, or edit_page, so an agent must infer the distinction from the operation name alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as move_page or copy_page that might achieve a similar looking result. The agent is told what the tool does but not when to reach for it over its siblings.

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