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 for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't mention required permissions, whether this is an atomic operation, what happens on failure, rate limits, or what the response contains. For a creation tool with complex nested parameters, this is inadequate behavioral context.

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. While front-loaded with the core action, it lacks necessary elaboration for proper tool selection and usage.

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 3 complex nested parameters, 0% schema description coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what an 'engagement' is in this context, what 'details' encompass, what happens after creation, or how this differs from other creation tools. The minimal description fails to provide adequate context for proper tool invocation.

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 nested parameters, the description 'with details' provides minimal insight into what parameters are expected. It doesn't explain the structure of 'engagement', 'associations', or 'metadata' objects, nor does it clarify required versus optional fields. 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 'Create a new engagement with details' clearly states the action (create) and resource (engagement), but it's vague about what 'with details' means and doesn't distinguish this tool from sibling tools like 'engagement_details_update' or 'crm_create_object'. It provides basic purpose but lacks specificity about what makes this tool unique.

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. With many sibling tools like 'calls_create', 'emails_create', 'meetings_create', and 'engagement_details_update', there's no indication of when this specific engagement creation tool is appropriate versus other creation tools or when to use batch alternatives.

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