Bulk Create Time And Material Timecards

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses critical behavioral traits: processing all records in one request, returning the resulting collection, and the fact that individual entries can fail independently so each must be checked. It also specifies error payload structure with common HTTP statuses, which is valuable context for handling failures. This goes well beyond the structured 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 dense but well-organized, starting with the primary purpose, then usage context, then behavior/error handling, then parameter notes, and finally the API reference. Every sentence adds value—no fluff or redundancy. The front-loaded purpose and guidance make it easy for an agent to quickly assess applicability.

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 tool's complexity (bulk array input, partial failures, default parameter, permission implications), the description covers all essentials: success behavior (returns resulting collection), partial failure semantics, error statuses, required parameters, default parameter behavior, and endpoint information. This is sufficient for an agent to select and invoke the tool correctly without an output schema, especially since the description also indicates the return type.

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 input schema already documents both parameters with descriptions, but the description adds meaningful semantics: project_id defaults to the value set by procore_set_config when omitted, and it reiterates the required parameters. This default behavior is not present in the schema, providing additional guidance. The description also clarifies the array parameter's role in a bulk operation context.

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 'Bulk create Time and material timecards with one request,' which clearly states the action (bulk create), the resource (time and material timecards), and the scope (bulk). It explicitly contrasts with repeated single-record calls, distinguishing it from sibling tools like create_time_and_material_timecard.

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 explicit usage guidance: 'Prefer this over repeated single-record calls when handling many time and material timecards at once.' This gives a clear when-to-use and implies when not to use (when only a few are needed). It also explains the default behavior of project_id from procore_set_config and lists common error conditions (401, 403, 404), helping the agent decide when this tool is appropriate.

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