ghl_product_inventory_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the tool is clearly safe. The description adds OAuth scopes and endpoint details but does not disclose rate limits, error handling, or response behavior beyond what annotations imply.

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 short with three clearly separated sections: a title, a purpose paragraph, and endpoint/scopes. It is efficient with no wasted words, though it could benefit from a bullet-style structure for the endpoint details.

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?

The description covers pagination and OAuth scopes, but lacks information about the response format, error handling, or rate limits. Given the absence of an output schema, the description could be more complete to guide the agent on expected return data.

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?

With 80% schema description coverage, the schema already documents most parameters. The description only generically mentions 'query parameters' without adding specific details about altId, search, or pagination behavior, so it provides minimal added value.

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 'retrieve a paginated list of inventory items', which is a specific verb-resource combination. The tool name and description distinguish it from sibling tools like 'ghl_product_list' (lists products) and 'ghl_product_inventory_update' (updates inventory).

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 says to use this endpoint to fetch details for multiple items based on query parameters, and mentions pagination. However, it does not explicitly state when not to use it or provide alternatives for single-item retrieval, leaving usage guidance implied.

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