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. It only states 'Get a Single Person' without disclosing behavioral traits like read-only nature, error handling, rate limits, or authentication requirements. For a retrieval 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 concise ('Get a Single Person') but under-specified. It's front-loaded but lacks necessary detail. The inclusion of the API path '[Resource Management/Resource Planning] GET /rest/v1.0/workforce-planning/v2/companies/{company_id}/people/{person_id}' adds technical context but doesn't improve clarity for an AI agent.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what a 'Person' resource contains, the response format, or error conditions. For a retrieval tool with 4 parameters, this leaves significant gaps for the 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 detailed parameter descriptions in the input schema. The description adds no parameter semantics beyond what the schema provides. Baseline 3 is appropriate when the schema does all the work.

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 'Get a Single Person' clearly states the verb ('Get') and resource ('Person'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_all_people_belonging_to_a_company' or 'get_all_people_belonging_to_a_group'. It lacks specificity about what 'single' means beyond the obvious.

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 on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites like authentication, nor does it contrast with list-style sibling tools. The agent must infer usage from the tool name alone.

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