Get Ad Accounts

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavioral traits: results are grouped by organization and filtered by user access permissions. But it does not mention side effects, authentication needs, rate limits, or pagination; 'Get' implies a read operation but unsupported behavioral detail is limited.

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?

Two tight sentences with no filler. The core action is front-loaded in the first sentence, and the second adds valuable grouping and access-filtering behavior. Every sentence 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?

For a single-parameter read tool with an output schema, the description covers the essential behavior: what is retrieved, how it is grouped, and how access is filtered. It lacks explicit alternative-usage guidance, but sibling resource names and the structured schema compensate. Overall sufficient for correct invocation.

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 100%, so the schema already fully documents org_ids. The description phrase 'specified organization IDs' merely restates the parameter in prose and adds no deeper semantic detail such as format, constraints, or behavior beyond what the schema provides. 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?

The description opens with a specific verb and resource: 'Get all ad accounts for specified organization IDs.' The second sentence clarifies the return content (ad account IDs and names) and the grouping/filtering behavior, clearly distinguishing this tool from sibling tools that target campaigns, ads, events, or performance reports.

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 the tool is used when ad account IDs and names are needed for specific organizations, and it notes access-permission filtering. However, it does not explicitly state when to prefer this tool over sibling tools or provide any exclusion conditions, relying instead on resource-name differentiation.

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