Bulk Delete Materials

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description repeats 'This cannot be undone' and 'Permanently removes,' which aligns with annotations but adds no new behavioral details beyond what is already declared.

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 four sentences, efficiently stating purpose, permanence, and required parameter. Minor repetition of 'cannot be undone' but overall concise and front-loaded.

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 simplicity (bulk delete, 2 parameters, no output schema) and annotations providing destruction and idempotency hints, the description adequately covers the core functionality. It lacks mention of response format but is sufficient for an informed 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?

Schema coverage is 100% (both parameters described in schema). The description only restates that project_id is required, adding no additional semantic context like ID format or constraints. Baseline 3 is appropriate.

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 'Bulk delete Material entries with one request.' It identifies the verb (delete), resource (materials), and scope (bulk), distinguishing it from single-delete siblings. The repetition of 'permanently delete' reinforces the action.

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 mentions 'Required parameters: project_id' and provides Procore API context, but does not specify when to use this tool versus alternatives like delete_material. No exclusions or when-not-to-use guidance is given.

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