Get acquisition item

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

The description adds no behavioral context beyond what the annotations already declare: readOnlyHint=true and openWorldHint=true. The phrase 'Read-only' duplicates the annotation rather than disclosing additional behaviors such as not-found handling, output shape, or whether the account parameter changes scoping.

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 extremely compact and front-loads the core purpose in the first sentence. The second sentence, 'Read-only,' is redundant with the readOnlyHint annotation but is brief and harmless; overall the structure wastes no words.

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?

Given the low complexity, complete parameter documentation, and safety annotations, the description is largely sufficient for an agent to invoke the tool correctly. A small gap is the lack of any statement about return contents when no output schema exists, but 'Retrieve' reasonably implies it returns the item.

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 provides complete descriptions for all three parameters, including the distinction between the acquisition GUID and the acquisition item GUID, and the account override behavior. The description adds no parameter-level meaning, so it rests at the baseline for full schema coverage.

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 ('Retrieve'), a precise resource ('a single item within an acquisition'), and a scope boundary that distinguishes it from sibling tools like get_acquisition, search_acquisitions, and get_item. It clearly communicates this is a targeted read of one acquisition item rather than a list or an unrelated item lookup.

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 gives no explicit guidance on when to choose this tool over alternatives, such as get_item, search_items, or get_acquisition. It does not mention exclusions, prerequisites, or related tools, so the agent must infer usage solely from the name and resource phrasing.

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