Create BIM File

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

Annotations already indicate this is not read-only, not destructive, not idempotent. The description adds that it returns the created object on success (HTTP 201) but does not elaborate on side effects, permissions, or constraints. Moderate added value.

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?

Four sentences, front-loaded purpose, then required params, then API reference. Every sentence contributes meaning. No 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?

For a simple create tool with 2 params and no output schema, the description includes the API endpoint, HTTP response code, and required parameters. It could mention potential errors or the need for authentication, but is sufficiently 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 both parameters adequately described. The description repeats 'Required parameters: project_id, bim_file' and a minor note from the schema but adds no new meaning beyond what 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?

The description clearly states the action (create) and resource (BIM File/record), and includes the Procore API endpoint. However, it does not explicitly differentiate from sibling tools like other create functions, but the specificity of 'BIM File' and 'Preconstruction > BIM' provides enough context.

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 says 'Use this to create a new BIM records in Procore' but lacks explicit guidance on when not to use or alternatives. Required parameters are listed, but no context for selecting this tool over similar ones.

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