delete-channel-section

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

No annotations are provided, so the description carries the full burden. It discloses that deletion is permanent, costs quota, and requires an explicit confirmation flag. These are critical behavioral traits beyond what the input schema states. It doesn't discuss side effects or prerequisites, but the key destructive nature is clearly communicated.

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 a single, compact sentence with all essential information front-loaded. It avoids redundant phrasing and earns its place by covering purpose, cost, and a critical parameter requirement in minimal words.

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 delete with two parameters and no output schema, the description covers the core aspects: permanent effect, cost, and confirmation requirement. It doesn't mention error scenarios or prerequisites, but given the tool's simplicity and the schema's completeness, it is sufficiently complete for an agent to invoke 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 100%, with both parameters already described. The description reiterates the confirm requirement but adds no new parameter-level detail. Baseline 3 is appropriate since the schema does the heavy lifting.

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: 'Permanently delete a channel section.' This clearly distinguishes it from sibling tools like create-channel-section, update-channel-section, and list-channel-sections. The word 'permanently' adds important scope about the operation's effect.

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?

Provides clear context for use: this tool deletes a channel section, costs 50 quota units, and requires confirm=true. It doesn't explicitly mention alternatives or when not to use it, but the practical guidance about confirmation and cost is useful. The context is clear enough for an agent to select it for deletion tasks.

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