get_account_details

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

With no annotations, the description must carry behavioral disclosure. It does convey a read-only retrieval action and the scope of returned data, which rules out mutation. It does not mention error handling, auth, or account-ownership restrictions, but for a simple getter the provided transparency is acceptable.

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, well-structured sentence front-loads the purpose and gives concrete examples of returned information. No 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?

For a one-parameter read-only retrieval, the description covers the resource, the key returned fields, and the account ID. It could mention response shape or error conditions, but nothing essential is missing for a caller with an accountId.

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 already documents accountId at 100% coverage, including the useful note that it is a numeric ID, not a URN. The description adds no extra parameter-level meaning beyond referring to 'a specific' account, so the baseline score 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?

States a clear verb ('Retrieves'), resource ('detailed information about a specific LinkedIn Ad Account'), and enumerates the kinds of data returned. It is unambiguous but does not explicitly distinguish itself from sibling list_ad_accounts or other get_* tools.

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 on when to use this over list_ad_accounts or when not to use it. The word 'specific' implies a caller already has an account ID, but the description leaves that inference to the agent.

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