List business profiles

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered by structured data. The description adds only the ownership scoping; it says nothing about pagination defaults (max_pages default 1) or how results merge across pages, though the schema partially covers those parameters.

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. It is efficient but arguably under-specified rather than maximally concise, since a scoping/alternative clause could be added at little cost.

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 read-only list tool with annotations and a partially documented schema, this is minimally adequate. Lacking an output schema, the description could state the shape of returned profiles or pagination behavior, and it does not distinguish itself from sibling profile-listing tools.

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 coverage is 75%, and business_id itself carries no schema description; the phrase 'owned by a business' implicitly explains that parameter but adds no format or ID-source detail. Pagination params are documented in the schema, not the description, so 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?

Specific verb (list) and resource (Reddit profiles) with the scoping qualifier 'owned by a business', which tells the agent this is business-scoped rather than account-scoped. However it never names or contrasts with the close sibling reddit_ads_list_account_profiles, so disambiguation requires opening the schema.

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?

No when-to-use, when-not-to-use, or alternative-tool guidance beyond the implicit business scoping. Nothing tells the agent how this differs from list_account_profiles or what prerequisites (e.g. valid business_id) exist.

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