Procore MCP Server

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

No annotations are provided, so the description carries the full burden. It states 'Delete' which implies a destructive operation, but doesn't disclose critical behavioral traits such as whether deletion is permanent, reversible, requires admin permissions, or has side effects (e.g., affecting app installations). This leaves significant gaps for a mutation tool.

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 concise with no wasted words, though the inclusion of the API endpoint '[Platform - Developer Tools/App Marketplace] DELETE /rest/v1.0/companies/{company_id}/app_configurations/{id}' is somewhat technical and may not aid an AI agent directly. It's front-loaded with the core action.

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 the tool's destructive nature, lack of annotations, and no output schema, the description is inadequate. It doesn't cover behavioral aspects like permanence, permissions, or error handling, nor does it reference sibling tools for context, leaving the agent under-informed for safe usage.

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 description coverage is 100%, with both parameters (id, company_id) clearly documented in the schema. The description adds no additional parameter semantics beyond the schema, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'Delete app configuration' states the action (delete) and resource (app configuration), which is clear but minimal. It doesn't specify what 'app configuration' entails or distinguish it from similar tools like 'delete_app_installation' or other deletion tools in the sibling list, leaving room for ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., needing specific permissions), consequences of deletion, or references to related tools like 'create_app_configuration' or 'list_app_configurations' for context.

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