Procore MCP Server

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

No annotations are provided, so the description carries full burden. 'Create' implies a write/mutation operation, but the description doesn't disclose any behavioral traits: no information about required permissions, whether this is idempotent, what happens on conflict, or what the response contains. The HTTP method 'POST' is mentioned, but this is structural rather than behavioral guidance for the agent.

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 ('Create drawing area. [Project Management/Drawings] POST /rest/v1.1/projects/{project_id}/drawing_areas'), but this brevity comes at the cost of being under-specified. The category and endpoint information are useful structural additions, but the core description lacks substance. It's front-loaded but incomplete.

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 creation/mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what a drawing area is, what the creation entails, what permissions are needed, or what the tool returns. The schema covers parameters, but the overall context for safe and correct usage is missing.

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 parameter documentation in the schema itself. The description adds no parameter semantics beyond what the schema provides—it doesn't explain relationships between parameters (e.g., that 'project_id' must reference an existing project) or provide examples. Since the schema does the heavy lifting, the baseline score of 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 'Create drawing area' is a tautology that restates the tool name without adding meaningful context. It lacks specificity about what a 'drawing area' is or what creation entails, though the category '[Project Management/Drawings]' provides minimal domain context. Compared to sibling tools like 'create_drawing_set' or 'create_drawing_upload', it doesn't distinguish its unique purpose.

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. There's no mention of prerequisites (e.g., needing an existing project), constraints, or related tools like 'create_drawing_set' or 'create_drawing_upload' from the sibling list. The agent receives zero usage direction.

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