zuckerbot_list_business_context

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It does not mention that the tool is read-only, non-destructive, or that it does not modify state. Also missing details like pagination, sorting, or error behaviors. The agent must infer the read-only nature from the 'list' verb.

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: the first defines the action and return, the second provides usage contexts. No extraneous information; every word contributes. Highly concise and front-loaded.

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?

The description covers the main purpose and return value (files with summaries), and provides practical usage examples. For a simple list tool with one optional parameter and no output schema, it is mostly complete. Minor gaps: no mention of error states or maximum results, but these are not critical.

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 has 100% description coverage, with the 'business_id' parameter already described as 'Optional business ID override'. The tool description adds no additional semantics beyond the schema. Baseline score 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?

Clearly states the verb 'List', the resource 'uploaded business-context files', and the scope 'for a business'. The description also includes the extracted summaries, providing a complete picture. This differentiates it from sibling tools like zuckerbot_upload_business_context.

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 states two specific use cases: confirming planning documents before creating a campaign and checking if a previous upload was processed successfully. This gives clear guidance on when to use the tool, though no explicit alternatives or when-not-to-use are provided.

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