delete-crm-v4-objects-objtype-objid_objid

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

With no annotations, the description carries full responsibility for disclosing behavior. It does not explain whether this is a soft delete (archive) or permanent delete, whether it is reversible, what permissions are needed, or what the response looks like. The word 'Archive' alone is insufficient.

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?

One word is not concise; it is grossly under-specified. There is no structure or useful information, so this is not an example of efficient conciseness but rather a lack of content.

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 delete/archive operation with no annotations, no output schema, and only one-word description, the tool is completely inadequate. The agent lacks essential context about side effects, error cases, and parameter semantics.

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 schema has descriptions for both parameters ('Path parameter objectId', 'Path parameter objectType'), but these are placeholders with no real semantic meaning. The tool description adds nothing, so an agent cannot infer what objectType values are accepted or how objectId should be formatted.

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?

Description is just 'Archive'. It fails to specify the resource (the CRM object identified by objectType and objectId) or the action clearly. This is essentially a tautology of the tool's name suffix and does not distinguish from sibling batch-archive tools.

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 on when to use this single-object v4 archive versus the many sibling batch-archive or delete alternatives. No context, prerequisites, or exclusions are provided.

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