engagement_details_create

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It states it's a creation operation but doesn't mention permissions required, whether it's idempotent, what happens on failure, or what the expected response format might be. 'with details' hints at richer input but doesn't clarify behavioral implications.

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 extremely concise at just 5 words, which is efficient. However, this conciseness comes at the cost of being under-specified for such a complex tool with multiple parameters and many sibling alternatives.

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 creation tool with no annotations, no output schema, 0% schema description coverage, and complex nested parameters, the description is severely inadequate. It doesn't explain what constitutes a successful creation, what data is returned, or how to handle the various parameter structures. The minimal description fails to provide necessary context for proper tool usage.

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?

With 0% schema description coverage and 3 complex parameters (engagement, associations, metadata), the description provides almost no parameter guidance. 'with details' vaguely references the engagement parameter but doesn't explain what details are expected, what associations mean, or how metadata is used. The description fails to compensate for the complete lack of schema descriptions.

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 states the basic action ('Create a new engagement') but lacks specificity about what distinguishes it from other engagement tools. It mentions 'with details' which hints at richer data than a basic create, but doesn't clearly differentiate from sibling tools like 'engagement_details_update' or 'calls_create'.

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. With multiple sibling tools for creating engagements (e.g., calls_create, emails_create, tasks_create), the description offers no context about when this general 'engagement_details_create' is preferred over more specific creation tools.

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