Bulk Delete Managed Equipment Maintenance Log Attachments

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description reinforces permanent deletion but adds no new behavioral traits beyond stating the endpoint path and required parameters. It does not describe side effects, authorization needs, rate limits, or response behavior. With annotations covering the basic destructive nature, the description adds limited value.

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 somewhat verbose, repeating 'permanently delete' and 'This cannot be undone' twice. It includes potentially useful API context (Procore API, endpoint path) but could be more concise. Some redundancy reduces efficiency.

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 tool has no output schema and the description does not explain what the response looks like (e.g., success message, affected IDs, error handling). It also lacks information on rate limits, prerequisites, or consequences beyond deletion. Given the bulk nature and permanent effect, more context is expected.

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?

Input schema has 100% parameter description coverage, so the baseline is 3. The description mentions required parameters (company_id, id) but duplicates schema info. No additional meaning or example values are provided for the array parameter 'managed_equipment_maintenance_logs_attachment_ids'. The description does not compensate for parameter semantics beyond what the schema already offers.

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: 'Delete multiple Managed Equipment Maintenance Logs Attachments with one request.' It specifies the verb (delete), resource (attachments of maintenance logs), and scope (bulk). The name and description together differentiate it from siblings like bulk_delete_managed_equipment_attachment, though it doesn't explicitly contrast them.

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 advises using this for permanent deletion ('This cannot be undone') and lists required parameters. However, it does not specify when to use this tool versus alternatives (e.g., single delete or other bulk delete endpoints). No explicit exclusion criteria or use-case guidance is provided beyond the command.

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