List my businesses

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

annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the meaningful detail that results are scoped to the authenticated user's memberships, but says nothing about authorization requirements for the role filter, pagination behavior, or result ordering. With annotations carrying the safety burden, this is an adequate but thin addition.

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?

A single front-loaded sentence with zero filler; every word earns its place and the resource and scope appear immediately.

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?

For a 5-parameter list tool with no output schema and no required parameters, the definition is only minimally sufficient: it never indicates what a business record contains or how pagination merges (max_pages) behaves across pages. Acceptable to invoke, but the agent is left guessing about return shape.

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 description coverage is 80%, so the baseline is 3. The description adds no parameter detail at all — notably the 'role' enum (BUSINESS_ADMIN/CATALOG_ADMIN) is undocumented in both schema and description, but the four pagination/filter parameters are reasonably explained by the schema itself.

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?

States a specific verb ('List') and resource ('businesses') with a clear scope qualifier ('the authenticated user belongs to'), which separates it from the singular reddit_ads_get_business. It does not, however, explicitly distinguish itself from adjacent siblings such as reddit_ads_list_business_ad_accounts or reddit_ads_list_business_profiles.

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 defines the result set but gives no when-to-use guidance, no prerequisites, and no mention of when to prefer get_business or another sibling. An agent must infer the calling context entirely.

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