surveymonkey_delete_page

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly warns that the operation is irreversible and discloses the cascade effect that all questions on the page are deleted. It does not mention permissions or failure modes, but the key destructive traits are covered.

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: it states the action, the irreversible warning, and then lists the two arguments. Every sentence adds meaningful information with no filler.

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 simple destructive tool with two required parameters, the description covers the action, scope, and irreversibility, and an output schema exists so return values need not be described. It omits authentication or error details, but those are not essential for invoking this tool correctly.

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 for missing parameter documentation. It merely restates the parameter names as 'Survey ID' and 'Page ID,' adding little beyond the schema property titles. It does not explain how to obtain these IDs or clarify any format expectations.

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: it deletes a page and all its questions from a survey. This clearly distinguishes it from sibling tools like delete_survey, delete_question, get_page, or update_page.

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 makes the scope and effect explicit, so an agent can infer when to use this tool rather than deleting a question or updating a page. It does not explicitly name alternatives or exclusions, but the effect statement is clear enough for correct selection.

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