Procore MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Delete' which implies a destructive operation, but doesn't clarify if this is permanent, reversible, requires specific permissions, or has side effects. The HTTP method (DELETE) is mentioned but without explaining what that means operationally. For a destructive tool with zero annotation coverage, this is inadequate.

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 with just two parts: the core statement and technical endpoint details. There's no wasted verbiage, and the information is front-loaded. However, the technical endpoint information could be considered extraneous for an AI agent's understanding of when to use the tool.

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 operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after deletion, whether there are confirmation steps, what permissions are required, or what the response contains. The technical endpoint is included but doesn't compensate for the lack of operational context needed for a deletion tool.

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 all three parameters (list_id, id, project_id) documented in the schema. The description adds no additional parameter information beyond what's already in the schema. The baseline score of 3 reflects adequate coverage when the schema does the heavy lifting, though the description doesn't add value here.

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 Checklist Section' clearly states the verb (Delete) and resource (Checklist Section), but it's a tautology that restates the tool name. The addition of '[Project Management/Inspections] DELETE /rest/v1.0/checklist/lists/{list_id}/sections/{id}' provides technical context but doesn't meaningfully differentiate it from sibling tools beyond confirming it's a deletion operation.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites, consequences, or when this deletion is appropriate versus other checklist modification tools. The sibling list includes many checklist-related tools, but no differentiation is offered.

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