sync_customers_from_inbox

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

With no annotations, the description carries the full burden. It discloses scanning all conversations, creating records for everyone who messaged, auto-tagging by platform, and no duplication. Lacks details on auth requirements or rate limits, but adequate for a simple import.

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?

Three sentences front-loading the purpose, with no extraneous words. Every sentence is informative.

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 presence of an output schema (not shown but confirmed) and the tool's simplicity, the description adequately covers behavior and intent. No need to detail return values.

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?

Only one parameter (org_id) with 100% schema coverage. Description adds no additional meaning beyond the schema's description. Baseline score of 3 applies.

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?

Description clearly states the verb 'import' and resource 'customers from social media inbox conversations'. It distinguishes from siblings like 'create_customer' (manual single creation) and 'list_customers' (querying existing records).

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?

Description implies usage for bulk import from inbox conversations, mentioning auto-tagging and no duplicates. However, it does not explicitly state when to use this tool versus alternatives (e.g., create_customer for individual additions).

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