Create Call Activity

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety and idempotency profile is covered externally. The description adds essentially no behavioral context beyond the annotations -- nothing about validation failures, whether the contact or deal must already exist, or what happens when callResult shape mismatches the call type.

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?

It is short and front-loaded, but the opening sentence duplicates the tool title and earns nothing, and a single line of real information carries the rest. Trimming the restatement would leave a tighter two-clause definition.

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 create tool with a single body parameter, the schema is fully self-describing (100% coverage) with nested required fields and descriptions on most properties, and the description at least clarifies that the deal association is optional. It omits that contact is also optional and says nothing about the polymorphic callResult, but the schema carries most of that burden.

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 100%, so the schema itself documents callTypeId, durationSec, callerUserId, and phone numbers, which sets the baseline at 3. The description only gestures at two of the many nested fields (contactId implicitly and dealId via "optionally associates it with a deal") and says nothing about the required callResult discriminator structure.

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 first line merely restates the tool name/title ("Create Call Activity"), which is tautological. The second sentence does add a specific verb and resource plus the optional deal association, but it frames the activity as being "for a contact" when contactId is in fact nullable in the schema, and it does not distinguish this from siblings such as log_email_activity or create_note.

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?

There is no guidance on when to use this versus log_email_activity or create_note, and no mention of prerequisites such as fetching a valid callTypeId via list_call_types or a caller user via list_users. The agent is left to infer that this is the write counterpart to list_call_activities/get_call_activity.

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