reset_draft

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 explicitly warns that the action is DESTRUCTIVE and irreversible, states that unpublished edits are lost, and instructs the agent to confirm with the user. This is exactly the transparency needed for a destructive mutation.

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 first, destructive warning second, user-confirmation instruction third, and arguments last. Every sentence earns its place with no filler or unnecessary detail.

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 two-parameter destructive tool, the description covers the operation, the risk, the required user confirmation, and both arguments. An output schema exists, so return-value documentation is not needed. The page/page_type scoping also prevents confusion with the blog-post reset sibling.

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. It names both required parameters and gives brief semantics: page_id is a HubSpot page ID and page_type is 'landing' or 'site'. The page_type values duplicate the schema enum, but the page_id clarification adds useful domain context absent 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?

The description states a specific action ('Discard draft changes') and a specific resource ('restore the draft to match the live version'). It clearly distinguishes this from update_page_draft, publish_page, and reset_blog_post_draft by scoping to pages with page_id and page_type landing/site.

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 implies when to use the tool: when you want to discard unpublished page draft changes and restore the draft to match live. However, it does not explicitly name alternatives or provide when-not-to-use guidance relative to sibling tools like update_page_draft or reset_blog_post_draft.

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