list_lead_sync_subscriptions

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

No annotations are provided, so the description carries the full burden. It only says 'list' and restates the required parameter, but discloses nothing about pagination, result format, read-only behavior, or failure conditions.

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?

The description is short and front-loaded, with no wasted words. However, the second sentence mostly restates the schema requirement rather than adding new decision-relevant information.

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 one-parameter list tool, this is minimally viable for invocation. But with no annotations and no output schema, it lacks useful context such as pagination behavior, return shape, or when to prefer this over get_lead_sync_subscription.

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 coverage is 100%, so the schema already fully documents ad_account_id. The description adds little beyond repeating that it is a required query param, which is the baseline behavior for high schema coverage.

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 action ('List'), the resource ('lead-sync subscriptions'), and the scope ('for an ad account'). It is distinguishable from the get/create/delete lead-sync siblings by context, though it does not explicitly differentiate itself from get_lead_sync_subscription.

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 when-to-use guidance is given versus alternatives like get_lead_sync_subscription, create_lead_sync_subscription, or delete_lead_sync_subscription. The 'Requires ad_account_id query param' note is a parameter constraint, not usage context.

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