engagement_details_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Create a new engagement' implies a write/mutation operation, but the description doesn't address permissions needed, whether the operation is idempotent, what happens on failure, rate limits, or what the response contains. For a creation tool with complex nested parameters and no annotations, this is a significant gap in 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. It's front-loaded with the core action and resource. While it's arguably too brief for such a complex tool, every word earns its place by communicating the essential purpose without any fluff or redundancy.

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's complexity (3 parameters with nested objects, no annotations, no output schema), the description is inadequate. It doesn't explain the relationship between this general engagement tool and the specific engagement type tools (calls_create, emails_create, etc.), doesn't clarify parameter usage, and provides no behavioral context for a creation operation. The description leaves too many open questions for effective tool selection and 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?

The schema description coverage is 0%, meaning none of the 3 parameters or their nested properties have descriptions in the schema. The description mentions 'with details' which hints at the 'engagement' parameter but doesn't explain what 'details' include or mention the 'associations' and 'metadata' parameters at all. This 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 verb ('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 'calls_create'. 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. There are many sibling tools for creating different types of engagements (calls_create, emails_create, meetings_create, etc.), but the description doesn't explain when to use this general engagement creation tool versus those specific ones, nor does it mention any prerequisites or constraints.

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