List Company'S Projects

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

Beyond the annotations, the description adds substantial behavioral detail: error payloads with common HTTP status codes (401, 403, 404), default behavior for company_id via procore_set_config, pagination mechanics, and the read-only nature. This significantly increases transparency and helps the agent anticipate various outcomes.

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 front-loaded with the primary purpose, followed by targeted usage, default behavior, return format, safety, troubleshooting, and API reference. Every sentence carries meaningful information without redundancy or fluff.

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?

Even without an output schema, the description explains the return shape as a JSON array, mentions pagination and remaining pages, and details error behavior. Combined with the annotations and schema, this is complete enough for an agent to successfully select and invoke the tool.

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?

The schema covers 100% of the parameters, providing a baseline of 3. The description adds extra meaning for company_id (defaults to procore_set_config when omitted) and explains how page and per_page control pagination and how the response reports remaining pages, which is more than the schema provides.

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?

Clearly states the verb and resource: 'Returns a list of Projects associated with a specified Company.' Also specifies the intended use case for discovering projects and looking up IDs, which helps distinguish it from other list tools in the sibling set.

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 explicit usage guidance: 'Use this to discover company s projects or to look up the id of one before calling a tool that needs it.' This tells the agent when to use the tool, but it does not explicitly name alternatives or exclusion criteria, so it falls just short of the highest bar.

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