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

Annotations declare a safe non-destructive mutation (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), and the description adds genuinely non-structural context: append-at-end behavior, a verified readback of the stored page number, the edit-survey right requirement, and the markComplete completion-counting effect. It does not discuss failure modes or what happens on repeated calls against non-idempotent behavior, which is the remaining gap.

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?

Front-loads the core definition and then packs distinctions, placement rule, and permission into a dense block with no filler sentences. It is on the long side and layers several concerns (routing, completion stats, placement, auth) into one paragraph, which slightly taxes scanning, but every clause carries 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?

With an output schema present, the description need not explain return values, and it covers everything else an agent needs: the tool's role in branching, the markComplete effect, the prerequisite page ordering, and the required permission. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the schema already documents code, message, and markComplete with their formats and defaults. The description largely restates markComplete's completion semantics and re-explains the message field, adding workflow linkage (using the returned pageNumber as a jump target) but little parameter meaning beyond the schema. Baseline 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?

States a specific verb and resource ('Adds a BRANCH-FINAL page to a survey') and immediately disambiguates it from the global-ending sibling set_end_message and from add_jump_logic_rule target='end'. An agent can identify exactly which page concept this creates without opening a schema.

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 contrasts the alternative routing mechanism (global ending via set_end_message vs. a jump to THIS page's number) and names the condition that selects each. It also gives the placement precondition (branching source question must sit on an earlier, separate page) and the required permission, so when-to-use is fully specified.

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