hubspot_delete_email_engagement

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

The disclosure 'soft delete' is valuable, indicating the action is reversible or not a permanent deletion. However, without annotations, the description carries full burden and lacks details on side effects, authentication needs, or error cases. It adds some transparency beyond the schema but is not comprehensive.

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 fluff or redundant information. Every word earns its place, making it highly concise and easy to read.

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 low complexity (single required parameter, no output schema), the description is fairly complete. It could mention the expected response or that a success indicator is returned, but this is acceptable for a simple deletion tool.

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 for the single parameter 'emailId' with its description. The description repeats this information ('The HubSpot email engagement ID to archive') without adding new meaning, so it meets the baseline but does not exceed it.

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 verb 'Archive (soft delete)' and the resource 'email engagement' in the context of HubSpot. It distinguishes from sibling delete tools like delete_contact or delete_deal by specifying the object type.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, no conditions for proper use, and no mention of when not to use it. For a delete operation, users might benefit from knowing about irreversibility or required permissions.

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