Delete Material

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds emphasis on irreversibility ('This cannot be undone' repeated) and provides the API endpoint and product area ('Procore API: Project Management > Field Productivity'), which are valuable behavioral traits beyond the 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 front-loaded with the purpose but contains redundancy: 'permanently delete' is repeated twice and 'This cannot be undone' is also repeated. It could be more concise.

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 (delete by two required IDs) and existing annotations covering destructiveness, the description provides adequate context: required parameters, API endpoint, and product area. No output schema exists, but description is not expected to detail return values. Missing info like error handling or dependencies, but overall sufficient.

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 has 100% coverage with clear descriptions for both parameters (id and project_id). The description only repeats that they are required, adding no additional meaning beyond the schema. 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 'Delete a specific Material' and 'permanently delete the specified Field Productivity records,' providing a specific verb and resource. It distinguishes itself from siblings like 'bulk_delete_materials' by focusing on a single material.

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 does not provide guidance on when to use this tool versus alternatives like 'bulk_delete_materials' or 'update_material.' It only mentions required parameters without any when-to-use or when-not-to-use context.

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