booking_pages_delete

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

With no annotations provided, the description fully discloses behavioral traits: soft-delete (row retained, is_active=false), public hiding, and re-activability. It also notes the required OAuth scope, covering safety and side effects.

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 two sentences with no filler. The first sentence immediately states the action, followed by key behavioral details and a scope requirement. Efficient and well-structured.

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 tool with one parameter and no output schema, the description provides complete context: what it does, how it works (soft-delete), how to reverse (update), and required permissions. Nothing critical 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 0%, but the description references 'by its event type ID', connecting the single parameter to the resource. It adds essential meaning beyond the schema (which only defines type and constraints), though more detail on the parameter format is absent.

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 clearly states the action 'Deactivate (pause) a booking page' and identifies the resource via event type ID. It distinguishes itself from siblings like booking_pages_create and booking_pages_update by explaining the soft-delete behavior and re-activation path.

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 specifies the required scope ('booking_pages:write') and mentions that re-activation is done via the update tool. It implicitly tells when to use this tool (to pause a page), but does not explicitly state alternatives or 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.