Delete Company Checklist Section

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description reinforces irreversibility by repeating 'cannot be undone' and 'permanently delete,' adding emphasis beyond annotations. However, it inaccurately refers to deleting 'Inspections' (the tool deletes a section, not inspections directly), and lacks disclosure of side effects (e.g., deletion of contained items).

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 structured with purpose first but includes redundant repetition ('cannot be undone' thrice). It could be more concise while maintaining clarity. The API endpoint line is informative but not strictly necessary.

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?

Given the destructive nature (no output schema), the description omits success responses, error conditions, and permissions. It does not clarify what happens to the section's items or provide operational context beyond deletion. This leaves gaps for an agent to understand full implications.

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?

With 100% schema description coverage, the baseline is 3. The description merely lists required parameters without adding meaning beyond the schema (e.g., format, constraints, or examples). It adds no extra semantic value.

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 'Deletes a Checklist Section for a specified Company,' establishing the verb and resource. The title and first sentence unambiguously convey the action. However, it does not explicitly differentiate from the project-level sibling 'delete_checklist_section,' though the 'company' prefix implicitly provides distinction.

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 lacks explicit guidance on when to use this tool versus alternatives, such as 'delete_company_checklist_template' or 'delete_checklist_section' (project-level). It only mentions required parameters without context on prerequisites (e.g., permissions) or exclusions.

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