get_ad_account

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Fetch' indicates a read-only operation, but the description does not disclose error behavior, return format, or permissions. For a simple get-by-id tool this is minimal but adequate.

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 sentence of seven words, front-loaded with the action and resource. Every word is meaningful and there is no redundant information.

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 tool is low complexity, but the description fails to explain the 'fields' parameter and provides no usage context or return expectations. It covers the core action but leaves meaningful gaps for an agent selecting and invoking the 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?

The schema includes two parameters ('id' and 'fields') with 0% description coverage. The description only mentions 'by id', which adds no semantic detail beyond the schema's property name, and it completely ignores the 'fields' parameter, leaving its purpose ambiguous.

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 uses the specific verb 'Fetch' and clearly identifies the resource as 'a single ad account' with lookup by 'id'. This distinguishes it from sibling tools like 'list_ad_accounts' (which fetches many) and 'get_campaign' (which fetches a different resource).

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 explicit guidance is given about when to use this tool versus alternatives like 'list_ad_accounts'. However, the phrasing 'by id' implies it is for retrieving one specific ad account, and the existence of an obvious list sibling provides implicit context.

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