Delete App Configuration

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

Annotations already indicate destructiveHint=true, but the description reinforces this with 'This cannot be undone' and 'Permanently removes', adding explicit warning. It also provides the API path. No contradiction with annotations. The description adds useful behavioral context beyond 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 front-loaded with the action but contains redundancy: 'This cannot be undone' appears twice. It includes an API path and Procore reference, which is helpful. However, the repetition of the irreversibility warning costs a point for conciseness.

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?

Given that there is no output schema and parameters are well-covered by the schema, the description adequately informs about irreversibility and required parameters. It also includes the full API endpoint for reference. For a delete tool, this is sufficiently 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 coverage is 100%, so the schema already documents both parameters with descriptions. The description mentions 'Required parameters: id, company_id' but does not add new meaning beyond what is in the schema. Baseline 3 is appropriate.

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 app configuration records, using specific verb 'Delete' and resource 'App Configuration'. It distinguishes from sibling tools by specifying 'App Marketplace records' and providing the exact API endpoint. There is no ambiguity; the purpose is unmistakable.

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 explicitly says 'Use this to permanently delete the specified App Marketplace records', giving clear context for when to use the tool. It lists required parameters but does not mention exclusions or alternatives. However, among the many delete tools, this one's purpose is narrow enough that the usage is implied.

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