zuckerbot_ad_accounts

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

With no annotations, the description carries the full burden. It discloses a behavioral side effect: 'this clears the stored page selection so you can pick a matching page.' This goes beyond simple listing and provides important context. It does not mention authentication or rate limits, but for a read-like operation, this is adequate.

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 concise, consisting of two sentences that front-load the main purpose and then add a clarifying detail about the selection side effect. Every sentence earns its place with no 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?

Given the simplicity of the tool (one optional parameter, no output schema, no nested objects), the description covers the purpose, usage context, parameter behavior, and an important side effect. It is complete for an agent to correctly invoke this tool.

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% for the single parameter select_id, and the parameter description in the schema is identical to the tool description's mention. Thus, the tool description adds no new semantic value beyond the schema. Baseline is 3, and no extra credit is warranted.

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 that this tool lists Meta ad accounts and shows the currently selected one, with an option to select a new account via select_id. It is specific about the verb (list/select) and resource (ad accounts), and distinguishes itself from sibling tools by its unique function of listing and selecting ad accounts.

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 explicitly says 'Call this during setup or when switching between multiple ad accounts,' providing clear context for when to use the tool. It does not explicitly state when not to use or mention alternatives, but the guidance is sufficient for an agent.

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