Create Call Log

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

The description adds context beyond annotations by stating that it returns a compact call log summary with duration in seconds, and it clarifies that the call type and user IDs must be resolved beforehand. No contradiction with the destructiveHint=true annotation is present.

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?

Four sentences, each providing necessary information: creation, required fields, lookup guidance, and response format. No filler 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 18 parameters and 6 required fields, the description covers the critical required fields, lookup dependencies, and return value. The schema and output schema handle optional fields and detailed structures, so the description is sufficient.

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 100% schema coverage, the description still adds value by naming which tools to use for resolving custom_call_type_id and user IDs, and by reinforcing the allowed related_to_type values. It does not repeat every parameter description but supplements the schema where lookups are needed.

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 uses the specific verb 'Creates' and identifies the resource as 'one Recruit CRM call log', clearly distinguishing it from sibling tools like update_call_log and search_call_logs. The singular 'one' clarifies scope.

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 explicitly explains when to use this tool by stating required fields and directing the agent to resolve call type IDs with list_call_types and user IDs with list_users. It also sets the constraint for related_to_type values, which is actionable guidance.

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