create_follow_up

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

The description includes the behavioral trait 'Auto-backed up', which indicates the action creates a backup. However, no annotations are provided, and the description omits other important traits like side effects (creates a record), idempotency, or required permissions.

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?

Two concise sentences with no waste. The first sentence effectively states the purpose and key features; the second adds a notable behavioral trait. Front-loaded and efficient.

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 absence of annotations, output schema, and parameter explanations, the description is incomplete. It does not cover return values, error conditions, or provide enough context for an agent to use the tool correctly with all 5 parameters.

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, the description adds no meaning to the 5 parameters beyond their schema titles and types. It does not explain formats (e.g., due_date), use of note, or enum values.

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 clearly states the tool creates a follow-up (task/call/email) linked to a deal. It uses specific verb+resource and distinguishes from sibling tools like add_note_to_deal or mark_activity_done.

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 explicit guidance on when to use this tool versus alternatives. The description only mentions auto-backup but does not specify prerequisites, when-not-to-use, or suggest other tools for different scenarios.

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