Create BIM Plan

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

Annotations already indicate this is a non-readonly, non-destructive, non-idempotent operation. The description adds context about required parameters and the HTTP 201 return, but does not disclose additional behavioral traits such as authorization needs, side effects, or rate limits. No contradiction with annotations.

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 with two sentences that front-load the core purpose and then provide essential details (required params, API reference). No extraneous information.

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 the simple parameter set (3 params, 2 required) and no output schema, the description covers the return value (created object on success with HTTP 201) and includes API categorization (Preconstruction > BIM) and endpoint path. This is sufficient for the agent to invoke the tool correctly.

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%, so the schema already documents all parameters. The description lists required parameters (project_id, bim_plan) and hints at 'view' as response schema view, but does not add significant new meaning beyond 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 the tool creates a BIM Plan within a Project, using the verb 'Create' and the resource 'BIM Plan'. It distinguishes from sibling tools like 'create_a_batch_of_bim_plans' by implying this is for a single BIM record. The success criteria (HTTP 201) further clarify the purpose.

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 provides a general usage statement ('Use this to create a new BIM records in Procore') and lists required parameters, but lacks explicit guidance on when to use this tool versus alternatives or when not to use it. Context is implied but not fully detailed.

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