fetch_businesses

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

No annotations provided; description states it returns Business IDs for further use, implies read-only nature. Does not detail pagination or rate limits, but adequate for a fetch tool.

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?

Eight sentences, no redundancy, logically ordered instructions (before, during, after), each sentence adds value.

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?

Covers prerequisites, filter constraints, and output (Business IDs). Missing explicit pagination behavior, but page/Page_size parameters are documented in schema.

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 covers 75% of top-level params with descriptions; description reinforces autocomplete requirement for certain filters and adds context about mandatory filters beyond 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 it fetches businesses from the Explorium API with filtering, and distinguishes from siblings like autocomplete, enrich_*, and match_businesses by explicitly warning against calling match_businesses afterwards.

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?

Provides explicit instructions: must call autocomplete first for filter values, do not use without available values, stop if filter unsupported, and suggests fetch_prospects for employee searches.

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