Get A Single Project

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

Beyond the read-only annotation, the description explains that it is read-only ('it changes nothing in Procore'), describes the return format (single JSON object), discloses defaulting behavior for company_id and project_id, and details common failure statuses (401, 403, 404). This adds substantial behavioral context.

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 dense but every sentence provides useful information: purpose, use case, defaults, return type, safety, error handling, required params, and API endpoint. It is not overly verbose for the amount of guidance it gives.

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 simple read operation, the description covers purpose, usage, parameters, behavior, return value, and error scenarios. No output schema exists, but the return type is clarified. The inclusion of the exact endpoint and API reference makes it complete 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 coverage is 100% with detailed descriptions for both parameters. The description adds value by explaining that the parameters default to values from procore_set_config when omitted, and reiterates that both are required, which is not fully captured in the schema.

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 clearly states 'Get a single project given a company ID and project ID' and specifies the use case 'when you already know which project you want and need its full field set.' This distinguishes it from list operations but does not explicitly differentiate it from the sibling tool 'show_project', which may perform a similar function.

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?

Provides a clear when-to-use: 'Use this when you already know which project you want and need its full field set.' It implies it is not for listing or searching, but does not explicitly exclude alternatives or mention when not to use it.

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