Delete App Configuration

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

Annotations already indicate destructive and non-read-only behavior, but the description adds significant context: deletion is permanent and irreversible, repeat calls return 404, and common error statuses (401, 403, 404) are explained with causes. This goes well 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 dense but logically structured: purpose, prerequisites, defaults, permanence, error handling, required parameters, and API endpoint. Some redundancy with schema (e.g., 'Required parameters: id, company_id') but every sentence generally earns its place.

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 no output schema, the description is thorough: it covers purpose, prerequisites, permanent effects, and error scenarios. Missing an explicit success response, and the company_id default/required contradiction are minor gaps, but overall it is quite complete.

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 has 100% coverage with basic descriptions for both parameters. The description adds that id must identify an existing parent record and that company_id defaults to procore_set_config, but this conflicts with the schema's required fields, creating ambiguity that undermines the added 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 the tool deletes an app configuration for a specified Procore company, using a specific verb and resource. It distinguishes itself from the many sibling delete tools by explicitly naming the resource and providing the exact API endpoint.

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?

It provides explicit prerequisite guidance: confirm the target id with the matching show/list tool before calling, and resolve id with the list tool first. It also notes company_id defaulting behavior. However, it does not explicitly state when not to use this tool or compare it to alternative deletion mechanisms.

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