Delete Rounding Configuration

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

The description adds significant behavioral context beyond annotations: it discloses permanence, non-repeatability (404 on repeat calls), and common error statuses (401, 403, 404). This complements destructiveHint:true and idempotentHint:true without contradiction, giving the agent a clear picture of consequences.

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 primary action and then provides structured, relevant details in subsequent sentences. It is longer than strictly necessary, but each sentence contributes meaningful context for a destructive operation, so it remains clear and organized.

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 one parameter and no output schema, the description covers all necessary context: the action, confirmation step, default parameter, error handling, and API reference. This is sufficient for an agent to invoke the tool safely and correctly.

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 covers company_id as a required URL path parameter, but the description adds the important detail that it defaults to the procore_set_config value when omitted. This extra semantic context is not in the schema, enhancing the agent's understanding.

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 a rounding configuration for the specified Procore company' and emphasizes the permanent removal. The inclusion of the endpoint and the directive to confirm the id with show/list tools clearly distinguishes it from sibling tools like create, update, or show.

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 usage guidance by instructing the agent to 'Confirm the target id with the matching show or list tool before calling.' It also mentions the default behavior of company_id from procore_set_config, but does not explicitly contrast with alternative tools beyond the show/list confirmation.

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