zuckerbot_get_audience_status

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

Discloses the side effect: 'Updates the local audience registry row'. Without annotations, the description carries the full burden, and this is a key behavioral trait. It also implies it's a read operation with a minor write, which is transparent.

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?

Two sentences, no fluff, front-loaded with purpose and usage. Every sentence adds value without redundancy.

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 tool with one parameter and no output schema, the description covers the action (fetch with side effect), the specific data fetched (delivery status, size, readiness), and the use case (pre-launch check). It is complete for an agent's needs.

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 already covers 'Stored audience row ID' for the single parameter. The description adds no new meaning beyond what the schema provides, so baseline 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 Meta delivery status, size, and readiness for a stored audience, with a specific verb and resource. It distinguishes from sibling tools like 'delete_audience' and 'refresh_audience' by focusing on checking status for campaign readiness.

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?

Explicitly says to use this tool to 'check if an audience is large enough to use in a campaign before launch'. While it doesn't mention alternatives or when not to use, this provides clear context for when to invoke it.

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