delete-crm-v3-properties-objtype-var_var

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

No annotations are present, so the description carries full burden. 'Archive' suggests a soft delete but does not disclose consequences, reversibility, or whether it permanently removes the property definition. It also doesn't mention any required permissions.

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 a single sentence with no wasted words. It is concise and easy to scan, though terse.

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 2-parameter delete with no annotations or output schema, the description is under-specified. It doesn't explain the impact of archiving, how it relates to other property operations, or what the response indicates. The agent has no context for usage or trade-offs.

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 provides descriptions for both parameters, but they are generic ('Path parameter objectType'). The description doesn't add semantic meaning to the parameters, leaving the agent to infer that objectType and propertyName identify the property to archive. Baseline 3 applies due to full schema coverage, but the descriptions are thin.

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 uses a specific verb ('Archive') and resource ('a property'), clearly identifying the action. However, it doesn't explicitly distinguish this singular property archive from sibling batch-archive endpoints, though the singular phrasing implies one property.

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?

No guidance is provided about when to use this tool versus alternatives like the batch archive or v4 delete endpoints. There are no prerequisites, exclusions, or context cues beyond the bare statement.

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