Bulk Delete Time And Material Timecards

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

Annotations already mark destructiveHint and idempotentHint, so the bar is lower. The description adds valuable context: permanence ('cannot be undone'), repeat call behavior (returns 404), and error payload details (401/403/404). It does not contradict annotations; 'repeat call returns 404' is consistent with idempotent side effects.

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 moderately long but each sentence adds functional value: bulk operation, pre-call confirmation, parameter nesting, default, permanence, error codes, and API reference. It could be slightly tighter; the 'Required parameters: project_id' and API path repeat schema info, but the overall structure is front-loaded and readable.

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 destructive bulk delete with no output schema, the description covers prerequisites, default behavior, side effects, repeat-call behavior, and error handling. It also includes API endpoint and module location. This is complete enough for an agent to select and invoke the tool correctly without additional assumptions.

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 baseline is 3. The description adds meaning beyond schema: 'Pass the record's fields as top-level arguments — they are nested under "time_and_material_timecards" in the request payload for you' clarifies parameter passing, and project_id defaulting to procore_set_config value is not in the schema. This enriches agent understanding.

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 verb ('Bulk delete'), resource ('Time and material timecards'), and scope ('with one request'). It also distinguishes itself from siblings by mentioning confirmation via matching show or list tool before calling, differentiating this bulk delete from single delete and other operations.

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 pre-call guidance ('Confirm the target id with the matching show or list tool before calling'), explains the default project_id behavior using procore_set_config, and identifies common HTTP error scenarios (401, 403, 404). It lacks an explicit 'when not to use' or comparison to specific sibling tools, but the context is clear.

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