Bulk Create Bid Forms

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

Beyond the annotations, it discloses partial failure semantics ('individual entries can fail independently'), project_id defaulting to procore_set_config, and specific HTTP error statuses (401, 403, 404). These details meaningfully extend the annotation-provided 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?

Every sentence contributes necessary behavioral or usage context—preference guidance, defaults, error handling, and required parameters—without fluff. The description is dense yet structured, starting with the core purpose and flowing logically into details.

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 bulk mutation tool with no output schema, the description covers return behavior ('returns the resulting collection'), failure modes, required parameters, and even includes the API endpoint and version. This makes the tool fully actionable 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?

With 100% schema coverage, the schema already documents all parameters. The description adds valuable context by noting project_id's config-defined default and that bid_package_id must reference an existing parent record, exceeding the baseline without duplicating schema details.

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 opens with 'Creates multiple Bid Forms in one request,' which uses a specific verb and clearly identifies the resource and its batch scope. It also differentiates from repeated single-record calls, making it distinct among siblings.

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?

It explicitly says 'Prefer this over repeated single-record calls when handling many bid forms at once,' giving direct when-to-use guidance. It also instructs resolving bid_package_id with the matching list tool first, providing a clear prerequisite.

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