get_ad_account

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

With no annotations, the description carries the transparency burden. It indicates a read operation ('Get') and lists the fields returned, but does not disclose additional behavior such as how the configured account is determined, error scenarios, or whether any non-read side effects exist. For a simple getter, this is adequate but not rich.

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 front-loaded sentence that uses a specific verb ('Get') and resource, and efficiently lists the key data points. Every word earns its place, with no unnecessary filler.

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 is reasonably complete for a simple getter with one optional parameter and no output schema. It names the key fields and clarifies the scope ('configured ad account'), though it does not explicitly explain how the account is configured or how this relates to multi-account scenarios (e.g., list_ad_accounts). This minor gap prevents a perfect score.

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 the single 'fields' parameter with a clear description and default value. The tool description does not add extra semantic meaning beyond the schema, so a baseline score of 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 clearly states the tool retrieves details of the configured ad account, listing specific data points (status, balance, currency, timezone, spend info). This distinguishes it from related tools like list_ad_accounts (which lists all accounts) and update_ad_account (which modifies).

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 the default/configured account but does not explicitly state when to use this tool versus alternatives like list_ad_accounts. No exclusions or alternative tool mentions are provided, making the guidance implicit rather than explicit.

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