Nordstrom MCP Server

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

No annotations are provided, so the description carries the full burden. It describes the tool's function and output fields, but does not disclose behavioral traits such as whether it's read-only (implied by 'Get'), error handling, rate limits, authentication needs, or response format. The description adds value by specifying the scope of details, but lacks operational context.

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, efficient sentence that front-loads the purpose and lists key details without redundancy. Every element (verb, resource, fields, target) earns its place, making it easy to scan and understand quickly.

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?

Given the tool's low complexity (single parameter, no output schema, no annotations), the description is reasonably complete. It specifies what data is retrieved, aiding the agent in understanding the tool's value. However, it lacks details on behavioral aspects like error handling or output structure, which could be beneficial for a read operation.

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 100%, with the schema fully documenting the single parameter 'product_id'. The description does not add meaning beyond the schema, as it only implies parameter usage ('for a specific Nordstrom item') without detailing syntax or format. Baseline 3 is appropriate since the schema handles parameter 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 clearly states the verb ('Get') and resource ('full product details'), specifying exactly what information is retrieved (description, features, sizes, images, pricing) and for what target ('a specific Nordstrom item'). It distinguishes this from sibling tools like search_products (which finds items) or check_inventory (which checks stock).

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 implies usage context by specifying 'for a specific Nordstrom item' and listing detailed fields, suggesting it's for retrieving comprehensive data after an item is identified. However, it does not explicitly state when to use this versus alternatives like search_products (for finding items) or check_inventory (for stock info), nor does it mention prerequisites or exclusions.

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