delete_status_page_section

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly discloses a destructive side effect: 'Resources in the section are removed too.' This is valuable beyond the basic 'delete' semantics and warns the agent about irreversible cascading behavior. It does not mention permissions or reversibility, but the cascade warning is a strong disclosure for a delete operation.

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?

Two short sentences with zero waste. The core action is front-loaded, and the critical side effect is stated immediately after. Every word earns its place.

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 delete tool with a fully documented schema, the description is nearly complete. The only missing context is explicit guidance on when to use this versus delete_status_page_resource, but the cascade warning and clear resource scope make the tool callable without that. The absence of an output schema is not a gap because delete operations typically return minimal confirmation.

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 100%, so the schema already documents both parameters. The description does not add parameter-specific meaning beyond what the schema provides. Baseline 3 is appropriate because the schema does the heavy lifting and the description adds no extra parameter context.

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 ('Delete'), a specific resource ('a section from a status page'), and adds a critical scope detail: 'Resources in the section are removed too.' This clearly distinguishes it from sibling tools like delete_status_page_resource and delete_status_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 implies when to use it (when you want to delete a status page section) but does not explicitly state when not to use it or mention alternatives. The sibling list includes delete_status_page_resource, which is a related alternative, but the description does not explicitly contrast them. The cascading deletion warning is a useful usage signal, but it is not framed as a when-to-use guideline.

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