Bulk Update Time And Material Timecards

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

Beyond annotations, the description discloses that project_id defaults to the value set by procore_set_config when omitted, returns the modified timecard on success, and details failure modes (401, 403, 404). While annotations already cover read-only/destructive hints, the added error handling and default behavior are valuable 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?

The description is compact and front-loaded with the primary purpose. It covers usage guidance, default behavior, returns, errors, required parameters, and the endpoint in five sentences with no 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?

The description provides purpose, usage guidance, default behavior, error semantics, and endpoint information. It is complete for a two-parameter tool with no output schema, though it stops short of explaining the item structure inside the time_and_material_timecards array.

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 described. The description adds extra value by explaining that project_id defaults to the procore_set_config value when omitted. It does not add detail about the time_and_material_timecards array items, but the schema already labels it as an array of objects.

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 ('Bulk update Time and material timecards with one request') and names the specific resource. It distinguishes itself from the sibling single-record update by explicitly recommending it for batch scenarios.

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 explicitly says 'Prefer this over repeated single-record calls when handling many time and material timecards at once', which gives clear guidance on when to use this tool instead of alternatives. It also notes the project_id default from procore_set_config, aiding setup.

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