hubspot_list_email_engagements

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

With no annotations, the description carries full burden. It only mentions pagination, lacking disclosure of ordering, rate limits, auth needs, or behavior when 'after' is omitted. Minimal beyond the basic hint.

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 efficient sentence with no wasted words. However, it could benefit from a bit more structure (e.g., separate lines for params) without much overhead.

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 tool has 3 parameters and no output schema, the description should summarize return format or behavior. It does not mention what the list returns, default ordering, or how pagination works end-to-end. Incomplete.

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 description coverage is 0%, and the description adds little meaning beyond the schema. It hints that 'after' and 'limit' are pagination parameters but does not explain the 'properties' array or confirm the role of 'after'. Inadequate compensation.

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 'List' and the resource 'email engagements' with 'pagination', making it specific. However, it does not differentiate from sibling tools like hubspot_search_email_engagements or other list tools, but the purpose is clear.

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 implies usage for listing with pagination but provides no guidance on when to use this tool versus alternatives (e.g., search_email_engagements for filtering). No when-not-to-use or explicit context.

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