zuckerbot_get_capi_config

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It discloses a critical constraint: the webhook secret is write-only, with reads only returning set and last4 fields. However, it could mention any required permissions or authentication context, but given the tool is read-only, the transparency is good but not exhaustive.

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 three sentences front-loaded with purpose, followed by usage guidance, then a behavioral note. Every sentence adds value and there is no fluff. It is well-structured for quick comprehension.

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 tool is a simple read with one optional parameter and no output schema, the description lists all returned fields (CAPI delivery, CRM source, currency, mappings, action source, webhook URL) and covers the important behavioral constraint on the secret. It is complete for an AI agent to understand what it does and what to expect.

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 single optional parameter 'business_id' is fully described in the input schema with a clear description. The description adds no additional meaning beyond the schema, and schema coverage is 100%, so the baseline of 3 is appropriate.

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 it fetches the Conversions API configuration for a business and lists specific fields: CAPI delivery, CRM source, currency, stage-to-event mappings, action source, and webhook URL. It distinguishes from sibling tools like set_capi_config and rotate_webhook_secret by emphasizing its read-only nature and the write-only secret behavior.

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?

Explicit guidance on when to use: 'Use this before configuring CAPI to see what is already set, or to audit the current event mapping.' Also specifies when not to rely on it for the full webhook secret and points to the sibling tool zuckerbot_rotate_webhook_secret as the alternative.

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