Bulk Delete Project Segment Items

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

Annotations already flag destructive and idempotent hints, and the description adds critical behavioral context: permanent removal, irreversibility, repeat calls returning 404, and error payloads with common HTTP status codes (401, 403, 404). This goes beyond the annotations and is especially valuable for a destructive operation.

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 front-loaded with the action and includes all essential information, but it is somewhat verbose with redundancy (e.g., 'Permanently removes' followed by 'This cannot be undone') and similar prerequisites repeated for different IDs. Each sentence earns its place, but it could be tightened.

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, the description covers prerequisites, permanence, repeat behavior, error semantics, API category, and endpoint. It does not explain success response format or potential bulk-specific limitations (e.g., max items, partial failures), which would be useful for an agent.

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 coverage is 100%, so the schema already documents each parameter. The description adds meaningful context by explaining the default behavior for project_id, the need to resolve segment_id to an existing record, and listing required parameters. This enhances understanding beyond the schema definitions.

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 tool deletes project segment items in a specified Procore project, with the verb 'deletes' and resource identified. However, it says 'a project segment item' rather than emphasizing the bulk nature, and it doesn't explicitly differentiate from the sibling tool delete_project_segment_item, relying on the title for that 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 provides clear prerequisites: confirm the target id with a show/list tool and resolve segment_id with a list tool first, and explains project_id defaults from procore_set_config. It doesn't explicitly state when to use this bulk version versus the singular delete tool, but the context and naming imply the use case.

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