list_accounts

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

Without annotations, the description discloses the internal walking mechanism ('walks /me/businesses → businesses/{id}/ad_accounts'), providing good insight into the tool's behavior. However, it lacks details on rate limits or authorization nuances.

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 a single, concise sentence with a helpful parenthetical, front-loading the core action and resource without unnecessary words.

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 explains the underlying API calls and the scope of results. Though an output schema exists, the description provides sufficient context for a list tool; however, details about potential pagination or limits are absent.

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?

With zero parameters and 100% schema coverage, the description adds context about the scope of results ('every account reachable'), meeting the baseline expectation for parameterless tools.

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 the action ('List') and the resource ('every Reddit ad account reachable with the current credentials'), differentiating it from sibling tools focused on performance, ad groups, ads, and campaigns.

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 implies usage for discovering accounts accessible to the current credentials but does not explicitly state when to use this tool versus alternatives or provide any exclusion conditions.

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