conduyt_sync_local_presence

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

No annotations are provided, so the description carries the full behavioral burden and does so: it discloses the destructive removal of non-matching pool members, the 50-match cap with sorted-order selection, the matching rules, the return shape (pool/added/removed/matched), and the requires settings:edit authorization.

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?

Front-loaded with the core action, then the IMPORTANT criteria block, then the return and permission notes. Every sentence carries operational information, though the criteria run together densely; it stays appropriately sized for a destructive sync.

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?

Despite no annotations and no output schema, the description covers preconditions, filtering logic, cap behavior, destructive removal, the return fields, and the required permission. Nothing an agent needs to invoke it safely is missing.

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 tool takes zero parameters, so the schema baseline is 4. The description goes beyond that by spelling out the implicit matching semantics (standalone LP/LocalPres in FriendlyName, voice-capable, US +1 E.164) that effectively define what the parameterless call will act on.

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?

Specific verb (sync) plus precise resource (dialer's Local Presence number pool) and source (the account's Twilio subaccount). An agent can distinguish it from nearby number-management siblings like list_call_flow_numbers or release_ring_group_number without opening any schema.

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?

States a clear precondition — name the Twilio number with the LP convention first, since 'buying a number is not enough.' It gives the three matching criteria that gate adoption. It does not name an alternative tool or a when-not-to-use case, keeping it just below a 5.

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