get_lead_sync_subscription

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly indicates a read operation via 'Get', which implies non-destructive behavior, but it does not describe response characteristics, error conditions, or how the optional ad_account_id affects the lookup.

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 a single, front-loaded sentence with no wasted words. It efficiently communicates the core operation and resource scope.

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 simple getter, the description is minimally adequate, but it omits the role of ad_account_id and any expected output or error behavior. Given no output schema and no annotations, the definition leaves some operational context to be inferred.

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 description coverage is only 50%, with subscription_id documented as 'leadsync_...', but ad_account_id has no description. The tool description adds no meaning beyond referencing 'by ID', so it does not compensate for the undocumented parameter.

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 states a specific verb ('Get') and resource ('lead-sync subscription') with a clear scope ('by ID'). It is immediately distinguishable from the sibling tools list_lead_sync_subscriptions, create_lead_sync_subscription, and delete_lead_sync_subscription, all of which imply different operations.

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 provides no guidance on when to use this tool versus alternatives, such as list_lead_sync_subscriptions for enumeration or create_lead_sync_subscription for new subscriptions. The 'by ID' phrasing implies targeted retrieval, but no explicit context or exclusions are given.

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