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 'Setup' which implies a write/mutation operation, but doesn't disclose whether this is idempotent, what permissions are required, if it overwrites existing taxonomies, or what happens on success/failure. The API endpoint hint (POST) suggests creation, but behavioral details are missing.

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 a single sentence with no wasted words. It's front-loaded with the core action and includes the API endpoint for technical context. However, the project management/field productivity tag feels somewhat extraneous without further explanation.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'setup' entails, what the expected outcome is, or any side effects. The agent lacks crucial context about what this tool actually accomplishes beyond the vague verb 'Setup'.

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%, so the schema already documents all three parameters (company_id, categories, types). The description adds no additional parameter semantics beyond what's in the schema. The baseline score of 3 reflects adequate coverage by the schema alone, but the description contributes nothing extra.

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 'Setup Managed Equipment Taxonomy' is essentially a tautology that restates the tool name. It adds the project management/field productivity context and API endpoint, but fails to specify what 'setup' actually means (e.g., create, configure, import dependencies). It doesn't clearly distinguish this from sibling tools like 'create_equipment_category' or 'bulk_create_managed_equipment'.

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 doesn't mention prerequisites, typical scenarios, or what makes this tool distinct from other equipment-related tools in the sibling list. 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.