zuckerbot_research_market

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

With no annotations provided, the description must carry full behavioral disclosure. It fails to state that this is a read-only operation, mention any authentication or rate limits, or note whether data is cached or real-time. The verb 'Get' implies non-destructive intent, but this is insufficient given the missing annotations.

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 concise sentences split logically: first lists outputs, second gives usage context, third adds secondary use case. No filler or repetition, making it quick to scan.

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 no output schema, the description partially covers output by listing market size, audience estimates, and benchmarks. However, it lacks details on format, time period, or constraints (e.g., does it return percentages or raw numbers?). For a simple tool, it is adequate but not fully complete.

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 input schema already covers both parameters with clear descriptions (e.g., industry: 'Industry/business category (e.g., fitness, dental)', location: 'City/region (e.g., United States)'). The description merely mentions 'industry and location' without adding any new semantic detail, so it adds no value beyond the schema.

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 tool retrieves 'market size, addressable audience estimates, and Meta ad benchmarks (CPL, CTR, CPM)' for a given industry and location. This specific verb ('Get') and resource enumeration distinguishes it from sibling research tools like 'zuckerbot_research_reviews' and 'zuckerbot_research_competitors'.

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 advises using this tool 'before creating a campaign' to set budget expectations and understand audience size, and notes it is 'also useful for proposals and client presentations'. This provides clear context, though it lacks explicit alternatives or when-not-to-use guidance.

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