list_inventory_parts

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

With zero annotations provided, the description carries full disclosure burden. It mentions pagination behavior, helping the agent understand this handles large datasets. However, it fails to disclose read-only safety, rate limits, or return structure that annotations would typically cover.

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 efficient sentences with zero waste. Core purpose front-loaded in first sentence; behavioral trait (pagination) follows. No redundancy with schema or name.

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?

Adequate for a simple paginated list operation with well-described parameters, but incomplete regarding sibling tool differentiation (search_parts vs list) and behavioral disclosure given lack of annotations and output schema.

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 coverage is 100% covering all three parameters. The description adds value by contextualizing limit/page as 'pagination' and framing locationId within 'Shopmonkey inventory,' adding business context beyond the technical schema definitions.

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?

States specific verb (List), resource (parts), and scope (Shopmonkey inventory). The mention of 'Shopmonkey inventory' implicitly distinguishes from search_parts (which may search external catalogs) and get_inventory_part (singular retrieval), though explicit comparison language would strengthen 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?

Mentions pagination support but provides no guidance on when to use this tool versus siblings like search_parts (advanced/pervasive search) or get_inventory_part (single record lookup). No when-not-to-use or prerequisite guidance.

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