manage_page

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

With zero annotations, the description carries full behavioral burden. It does disclose the key side effect that deleted page items move to the first page, which is genuinely useful and non-obvious. But it says nothing about permissions, reversibility, whether add returns the new page id, or whether move is destructive/reordering across pages.

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?

One compact sentence with a parenthetical per action — front-loaded, zero filler, and easily scannable. Every clause earns its place by tying parameters to operations.

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?

For a four-action mutation tool with no annotations and no output schema, the description covers action-parameter mapping and one side effect but omits return values, error conditions, and index/ordering semantics. Adequate to attempt a call, not adequate to call confidently in edge cases.

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%, so the description must compensate, and it does by mapping each parameter to its action: name for add, id+name for rename, id for delete, id+index for move. Gaps remain — index base (0 vs 1), what 'id' refers to (page vs board), and that 'action' is required are left implicit.

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+resource (managing pages) and enumerates the four concrete operations, so an agent can immediately tell it apart from list_pages and read_board. It does not explicitly name a sibling as an alternative, but the resource scope is unmistakable.

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 action list implies which operation to pick for a given intent, and the delete note implies a fallback behavioral consequence. However, there is no explicit when-to-use vs list_pages guidance, no prerequisites (e.g., page id acquisition via list_pages), and no statement of when NOT to use it.

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