delete_section

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

The description discloses that tasks are moved to the parent project, which is a behavioral trait beyond deletion. However, it does not explicitly state that the deletion is permanent or irreversible, nor mention any required permissions or 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 concise with two sentences: one functional statement and one parameter list. No redundant information; front-loaded with the key behavior.

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 operation with one parameter and an output schema available, the description covers the core function and parameter adequately. Minor omission: could mention that deletion is irreversible.

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 'Args' section provides a brief description for the single parameter ('ID of the section to delete'), adding basic meaning beyond the schema. However, with 0% schema coverage, more detail (e.g., format, source) would improve clarity.

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 'Delete a section' and its side effect 'move its tasks to the parent project', distinguishing it from siblings like create_section, update_section, and list_sections.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or exclusions provided. The description only states the function without context for selection.

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