iter_inventory

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

No annotations are provided, so the description bears full responsibility. It discloses that the tool returns a flat JSON array with all vehicles, but does not mention error handling, performance implications for large datasets, or behavior when account_id is invalid. Minimal disclosure beyond the basic return structure.

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 concise: one sentence for purpose, one for usage guidance, and one example. Every word serves a purpose with no redundancy. Structure is clean and front-loaded.

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 tool's simplicity (one parameter, no nesting, existing output schema), the description covers purpose, usage, and provides an example. It lacks details on error handling or edge cases, but for a straightforward listing tool, it is largely complete.

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 description coverage is 0%, so the description must compensate. It only provides an example (account_id=1042) without explaining what account_id represents beyond 'dealer account.' No format, range, or semantics are given, leaving interpretation to the schema's minimal title 'Account Id.'

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 clearly states 'Yield all inventory vehicles for a dealer account as a flat JSON array,' specifying the action (yield), resource (inventory vehicles), and scope (all, no pagination). It also distinguishes from siblings like list_inventory by explicitly mentioning 'without pagination math.'

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 includes a direct 'Use when' guideline: 'every vehicle on the lot' without pagination math, which clearly indicates when this tool is appropriate. It implicitly distinguishes from paginated alternatives (e.g., list_inventory) by focusing on complete retrieval.

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