propack_inventory

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

With no annotations, the description carries the full burden, and it does disclose one behavioral trait: Web Terminal is intentionally not wrapped. However, it does not state whether this is a read-only reference operation, whether the mapping is fetched live or static, or what kind of output is returned beyond an implicit mapping.

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?

Two short sentences, with the core purpose front-loaded and the scope exclusion in the second sentence. Every sentence earns its place and there is 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 zero-parameter tool with a rich sibling list and an output schema, the description covers purpose, licensing relevance, and a notable omission. It is complete enough, though a sentence describing the expected output shape would remove residual ambiguity.

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 has zero parameters, so there is no parameter burden for the description to carry; the nominal 100% schema coverage makes this a baseline-4 case. The description adds no parameter semantics, but none are needed.

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 ('Map'), a clear resource ('every Pro Pack feature'), and the destination ('the curated tool that covers it'), so an agent can tell this is a feature-to-tool reference rather than a generic inventory operation. It draws a boundary by explicitly excluding Web Terminal, but it does not explicitly contrast with sibling inventory tools such as inventory_list or inventory_this.

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 licensing note ('Modern licenses include Pro Pack') gives context for when the mapping is relevant, and the Web Terminal exclusion tells users not to expect a wrapper for that feature. It does not name alternatives or state 'use this when...' directly, but for a zero-parameter reference tool the usage situation is strongly implied.

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