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 mutation, but does not disclose any behavioral traits such as whether deletion is permanent, reversible, requires specific permissions, has side effects (e.g., affecting financial records), or what happens on success/failure. The description is minimal and lacks critical safety and operational context.

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 extremely concise ('Delete billing period. [Construction Financials/Commitments] DELETE /rest/v1.0/projects/{project_id}/billing_periods/{id}'), but this brevity comes at the cost of clarity and completeness. The inclusion of the HTTP method and path is structural but not necessarily helpful for an AI agent without further context. It is front-loaded but under-specified.

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 this is a destructive mutation tool with no annotations and no output schema, the description is insufficient. It does not explain what a billing period is, the impact of deletion, error conditions, or return values. The agent lacks the context needed to use this tool safely and effectively in a financial/commitments domain.

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 clear descriptions for both parameters: 'project_id' as 'Unique identifier for the project' and 'id' as 'Billing Period ID'. The description adds no additional parameter semantics beyond what the schema already provides, so it meets the baseline of 3 for high schema coverage without adding 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 'Delete billing period' is a tautology that restates the tool name 'delete_billing_period' without adding specificity. It mentions '[Construction Financials/Commitments]' which provides some context about the domain, but does not clearly distinguish what a 'billing period' is or what deletion entails beyond the obvious verb+resource pairing.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, consequences, or any sibling tools (like 'create_billing_period' or 'list_billing_periods' which exist in the sibling list) that might be relevant. The agent is left with no usage context.

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