Bulk Delete Company Segment Items

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

The description discloses that the deletion is permanent and cannot be undone, that a repeat call returns 404, and that failures return HTTP status codes (401, 403, 404). This adds significant context beyond the annotations (destructiveHint: true), and there is no contradiction with the annotations.

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 information-dense and well-structured, with clear logical flow: statement of action, prerequisites, defaults, permanence, error behavior, required parameters, and API/endpoint details. It is slightly verbose but every clause provides value.

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 destructive bulk delete with no output schema, the description adequately covers what to confirm beforehand, default behavior, irreversibility, and error scenarios. It could mention the success response (e.g., 204), but that is not critical given the tool type.

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 schema already provides descriptions for all three parameters, but the description adds meaning beyond it: company_id defaults to the configured value when omitted, segment_id must identify an existing parent record, and segment_item_ids is the list of item IDs to delete. This goes beyond schema descriptions.

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 tool as deleting a company segment item for a specified Procore company, with a specific verb and resource. However, it does not explicitly mention the bulk nature (deleting multiple segment items via an array) or differentiate from the sibling tool delete_company_segment_item.

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 provides explicit usage guidance: confirm the target id with the matching show or list tool before calling, and resolve the segment_id with the matching list tool first. It also explains that company_id defaults to the value from procore_set_config. It does not explicitly state when to use this over the single-delete sibling, but the tool name and endpoint imply bulk usage.

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