list_businesses

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

No annotations are provided, so the description carries the full burden. It discloses pagination behavior ('Returns paginated results') and implicitly states read-only nature via 'List', and scopes access. It does not mention rate limits or ordering, but for a simple read operation this is reasonable transparency.

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 two concise sentences, front-loaded with the purpose and includes essential behavioral info (pagination). No wasted words or redundant details.

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 tool is simple with no output schema; the description adequately covers what it does and that results are paginated. It does not detail the return object shape or ordering, but these are less critical for a low-complexity list tool that is clearly scoped. It could mention that it returns business objects, but the name implies this.

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% coverage for all three parameters (after, limit, fields) with clear descriptions. The tool description adds only the pagination detail that maps to 'after' and 'limit', but does not add new semantic value beyond the schema. 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 uses a specific verb ('List') and resource ('all businesses accessible by the current user'), clearly distinguishing it from sibling tools like get_business (singular), list_business_ad_accounts, and list_business_users. The scope and pagination note make the purpose unambiguous.

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 gives clear context—'all businesses accessible by the current user'—which indicates the tool’s scope. However, it does not explicitly state when to prefer this over alternatives like get_business for a single entity, or other list tools, though the context is sufficient for most agents.

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