Get ad account

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 usefully adds what data surface is returned, but says nothing about auth requirements, the REDDIT_ADS_ACCOUNT_ID fallback behavior, or rate limits. With annotations present, a 3 is appropriate.

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 no filler; the resource is named immediately and the returned fields follow inline. Every clause earns its place.

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?

There is no output schema, so listing the returned fields (currency, time zone, attribution, approval status, exclusions) genuinely compensates for the missing return contract. Combined with the 100%-documented parameter and read-only annotations, the definition is nearly complete for a simple fetch tool.

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 100% and the single ad_account_id parameter is fully documented in the schema (t2_/a2_ format plus the REDDIT_ADS_ACCOUNT_ID default). The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb (Get) and resource (ad account) and enumerates the returned fields (currency, time zone, attribution settings, approval status, exclusions). This clearly distinguishes it from the plural sibling reddit_ads_list_ad_accounts, though it never explicitly names that contrast.

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?

Usage is only implied: the singular resource and field list suggest fetching one account's details, but there is no explicit statement of when to prefer this over reddit_ads_list_ad_accounts, reddit_ads_query_ad_accounts, or reddit_ads_get_ad_account_history.

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