direct_get_inventory

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates the operation is a 'get' (implying read-only), but it does not disclose auth requirements, rate limits, whether responses are raw provider payloads, or whether any allowlisting violations will cause failures. The description adds minimal context beyond the tool name and action.

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 focused sentence with no filler. It front-loads the core action and scope and does not repeat information already present in the schema.

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 low-level tool with two generic parameters and zero annotation coverage, the description is under-specified. It does not explain the inventory allowlist, how to select the service, what params to pass, or what behavioral constraints apply. The presence of an output schema helps but does not make this contextually complete for an agent deciding to invoke the tool correctly.

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%, and the only parameters are generic 'service' and 'params'. The description suggests a provider-native passthrough but gives no indication of what values 'service' should take, how 'params' should be structured, or which Direct inventory operations are allowed. It does not compensate for the lack of schema documentation.

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 names a specific verb ('Run') and a clear target ('provider-native get against the explicit Direct inventory allowlist'), which distinguishes it as a low-level passthrough read rather than a wrapper like direct_get_campaign. However, 'inventory allowlist' is not defined, so the exact resource remains somewhat ambiguous without external context.

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 on when to choose this tool over siblings such as direct_get_campaign, direct_get_statistics, or direct_write. The phrase 'explicit Direct inventory allowlist' implies a constrained scope, but it does not explain the conditions under which an agent should use this raw get instead of higher-level alternatives.

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