Bulk Delete BIM Model Revision Viewpoints

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

Annotations already indicate destructiveHint=true and permanent deletion. The description reinforces 'cannot be undone' but adds no new behavioral context beyond what annotations and schema provide. Repetitive.

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 repetitive ('cannot be undone' stated three times). It could be more concise by removing redundancy while retaining essential info.

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 annotations, high schema coverage, and straightforward delete operation, the description is adequate. It covers the essential purpose, permanence, and required parameters, though it lacks details on response or return behavior.

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 already describes both parameters with 100% coverage. The description only restates required parameters, adding no semantic value beyond the schema.

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 multiple BIM Model Revision Viewpoint associations in a single request,' specifying the verb (delete), resource, and scope (multiple, single request). This distinguishes it from a single-delete sibling by the name alone.

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 says 'Use this to permanently delete...' but does not provide guidance on when not to use it, nor does it mention the single-delete alternative. It lacks explicit usage boundaries.

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