getAccountInfo

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

With no annotations provided, the description carries the behavior disclosure burden. 'Get' clearly signals a read-only operation and the listed fields imply the response content, but no details are given about permissions, error conditions, data freshness, or any side effects. This is adequate for a simple getter 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 with no wasted words. It begins with the action and resource, then lists the useful detail categories, making it immediately scannable for an agent.

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?

This is a low-complexity, single-parameter read tool with no output schema. The description names the main output areas—currency, timezone, status, and linked business—which is enough for an agent to anticipate the return value. It lacks usage-alternative context, but that is partially addressed elsewhere in this evaluation.

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, documenting accountId as an ad account ID in act_XXX format. The description adds no additional parameter semantics, but the schema already fully explains the required input, so the baseline 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 states a specific verb and resource: 'Get detailed information about an ad account' and names concrete data categories: currency, timezone, status, and linked business. It is clear, though it does not explicitly distinguish itself from siblings like getBillingInfo or discoverAdAccounts.

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?

There is no guidance about when to use this tool versus alternatives. No mention of when to prefer getAccountInfo over getBillingInfo or discoverAdAccounts, and no exclusions or prerequisites are stated.

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