engagement_details_create

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

No annotations are provided, so the description carries full burden. It states 'Create a new engagement' which implies a write/mutation operation, but it doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens on failure, rate limits, or what the response looks like. For a creation tool with complex nested parameters, this lack of behavioral context is a significant gap.

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 with just one sentence ('Create a new engagement with details'). It's front-loaded with the core action and wastes no words, though this brevity contributes to underspecification in other dimensions. Every word earns its place in this minimal statement.

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 complexity (3 parameters with nested objects, no annotations, no output schema), the description is incomplete. It doesn't explain the engagement types (EMAIL, CALL, etc. from schema), the purpose of associations/metadata, what 'details' refers to, or what the tool returns. For a creation tool with rich input structure, this leaves too many gaps for effective agent use.

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%, so the schema provides no parameter descriptions. The description adds minimal value with 'with details', hinting at additional parameters beyond basic creation, but it doesn't explain what the three parameters (engagement, associations, metadata) mean or how they relate. This partially compensates but leaves most semantics undocumented, meeting the baseline for moderate schema coverage gaps.

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 'Create a new engagement with details' states the basic action (create) and resource (engagement), but it's vague about what 'engagement' means and what 'details' encompass. It doesn't distinguish this tool from sibling tools like 'calls_create', 'emails_create', or 'engagement_details_update', leaving ambiguity about when to use this specific creation tool versus others.

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 on when to use this tool versus alternatives. With many sibling creation tools (e.g., calls_create, emails_create, notes_create), the description offers no context about whether this is a generic engagement creator or specific to certain types, nor does it mention prerequisites or exclusions. This leaves the agent guessing about appropriate use cases.

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