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

Beyond the annotations, the description discloses refusal conditions, required permissions, positional renumbering effects, readback verification, and the returned page-list content. This meaningfully expands on the destructiveHint and non-idempotent hints.

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 compact and front-loaded: purpose and return value come first, followed by parameter meaning, constraints, renumbering behavior, verification, and permission requirements. Every sentence adds operational 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?

For a destructive survey-page mutation, the description covers the action, return side effect, parameter constraints, permission requirement, failure cases, and post-delete renumbering. With an output schema present, the return-value summary is additional rather than necessary, but nothing important appears 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 baseline is 3, but the description adds relevant parameter behavior by explaining that page numbers are positional and later pages renumber after removal. The moveQuestionsTo requirement is also repeated in context, reinforcing when it must be supplied.

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 states a specific verb and resource (deletes a page from a survey) and clarifies that it returns the current page list. It is clearly distinguishable from sibling operations such as delete_question, add_survey_page, and reorder_survey_pages.

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 description gives important usage conditions: if the page has questions, moveQuestionsTo is required or the delete is refused; the last page cannot be deleted; and edit-survey permission is required. It does not name alternative tools or explicitly contrast when another page operation should be used instead.

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