Delete Project Distribution Group

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

Annotations already indicate destructive and non-read-only behavior. The description adds that the deletion is permanent, cannot be undone, repeat calls return 404, and common error statuses (401, 403, 404) are explained. This is rich behavioral context beyond 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 compact but dense, covering action, prerequisites, consequences, errors, and endpoint in a short paragraph. Each sentence contributes useful information, though it could be slightly better organized by separating the required-parameters clarification.

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 tool with no output schema, the description covers prerequisites, permanence, repeat behavior, and failure modes well. The only gap is the internal inconsistency about whether project_id can be omitted, which slightly reduces completeness.

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 describes both parameters at 100% coverage. The description adds default behavior for project_id (from procore_set_config) and requires distribution_group_id to reference an existing record. However, it also states 'Required parameters: project_id, distribution_group_id,' which conflicts with the project_id default statement, creating ambiguity.

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 starts with a clear verb+resource statement: 'Delete a Distribution Group associated with the given Project.' It also names the exact Procore API endpoint (DELETE /rest/v1.0/projects/{project_id}/distribution_groups/{distribution_group_id}) and distinguishes from sibling create/list/update tools.

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 instructs the agent to confirm the target id with the matching show or list tool and to resolve distribution_group_id with the list tool first. It gives clear preconditions for use, though it does not explicitly mention alternative tools for non-delete operations.

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