remove_section

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

With no annotations, the description carries the burden of disclosing behavior. It explicitly states that the section is removed and its page is deleted, which reveals a destructive side-effect. However, it does not mention irreversibility, required permissions, or any additional cascading effects beyond the page deletion.

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, efficient sentence with no wasted words. It front-loads the primary action and immediately communicates the important destructive effect.

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?

Although the tool has only two parameters and an output schema exists, the description is too sparse for safe invocation. It lacks parameter semantics, usage guidance, and sufficient behavioral context for a destructive operation. The agent would have to infer the roles of slug and section_id without explicit support.

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?

The input schema has 0% description coverage, and the description does not explain how 'slug' and 'section_id' are used. It only says 'remove a section,' which maps weakly to section_id, but leaves slug completely unexplained. The description adds no meaningful parameter information beyond the schema's property names.

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 identifies the action ('Remove a section') and its direct consequence ('delete its page'). It distinguishes this from sibling tools like add_section, update_section, and delete_site by specifying a distinct removal operation on a section and its associated 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?

There is no guidance about when to use this tool versus alternatives, no prerequisites, and no mention of when not to use it. The only implied context is that this tool removes a section, but the description does not explicitly route the agent toward it or away from similar tools like delete_site.

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