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 mentions 'Bulk Create' and includes an API path hint ('POST'), implying a write operation, but doesn't disclose behavioral traits like required permissions, whether it overwrites existing memberships, rate limits, or error handling. The description adds minimal value beyond the name.

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—two brief phrases—and front-loaded with the core action. However, the API path detail ('[Core/Directory] POST /rest/v1.0/projects/{project_id}/project_memberships/bulk_add') is extraneous for an AI agent and could be omitted for better focus.

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 complexity of a bulk creation tool with no annotations or output schema, the description is insufficient. It lacks details on what 'party_ids' represent (e.g., user IDs, roles), the expected outcome, error scenarios, or how it differs from sibling tools, leaving significant gaps for an agent.

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 descriptions in the schema ('Unique identifier for the project' and 'party_ids'). The description adds no additional parameter semantics, but the schema provides adequate documentation, meeting the baseline for high coverage.

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 'Bulk Create Project Memberships' states the action ('Bulk Create') and resource ('Project Memberships'), which is clear but basic. It doesn't specify what 'memberships' entail or differentiate from similar tools like 'bulk_add_company_users_to_projects_v1_1' or 'add_company_user_to_project' in the sibling list, leaving the purpose somewhat vague.

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. With many sibling tools for adding users/memberships (e.g., 'add_company_user_to_project', 'bulk_add_company_users_to_projects_v1_1'), there's no indication of context, prerequisites, or distinctions, making it unhelpful for selection.

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