direct_get_inventory

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so safety is covered. The description adds one genuinely useful behavioral fact: operations are constrained to an explicit allowlist, meaning non-allowlisted services will be rejected. It does not say what happens on an allowlist miss or whether output mirrors the provider shape.

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 front-loaded sentence with no filler, but it is too terse for a nested, two-required-parameter passthrough tool. Concision is achieved at the cost of substance rather than by eliminating waste.

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?

An output schema exists so return values need no explanation, but the tool has two required parameters, a nested free-form object, and 0% schema coverage, and the description does not explain valid services, param shapes, or a usage example. For this complexity level it leaves the agent without enough to call it 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 both parameters are generic and undocumented ('service' string, 'params' free-form object with additionalProperties). The description's mention of an 'explicit allowlist' hints that 'service' is constrained but never enumerates valid values or explains how 'params' maps to the provider call, so the compensation required at 0% coverage is absent.

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 phrase 'provider-native get against the explicit Direct inventory allowlist' largely restates the tool name in jargon rather than naming a concrete resource. It implies a passthrough read restricted to a whitelist of Direct services, but an agent cannot tell what objects it actually returns.

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 statement of when to use this instead of the many typed siblings (direct_list_campaigns, direct_get_campaign, direct_get_statistics, etc.). The only hint is the 'allowlist' framing, which weakly implies a raw escape hatch, but no alternative is named.

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