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

The annotation readOnlyHint=true already discloses that this is a read-only operation. The description adds scoping context ('trending products and verified dropship inventory'), which is a mild behavioral constraint about what the search targets. Yet it does not elaborate on pagination, rate limits, authentication, or response behavior. With annotations covering the safety profile, a 3 is appropriate for the added scoping context but no richer behavioral disclosure.

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, front-loaded sentence that states the action and resource immediately. There is zero filler or redundancy—every word contributes to understanding the tool's purpose.

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 simple read-only search tool with only two optional, schema-documented parameters, the description gives enough context to call it correctly. There's no output schema, but the purpose is clear and the annotations cover the read-only aspect. The only missing piece is any mention of response format or sorting, but this is minor given the low complexity.

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%, so both query and max_price are already documented in the input schema. The description adds no parameter-specific meaning beyond what the schema provides—it doesn't clarify formats, defaults, or relationships. Baseline 3 applies because the schema does the heavy lifting.

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 a specific action ('Search') against a specific resource ('Northside Intelligence Smart Store catalog') and scopes it to 'trending products and verified dropship inventory.' This distinguishes it from sibling search tools like mf_search_coaches or ni_grantbot_search by naming a unique resource and domain.

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 implied usage is clear: use this when you need to search the smart store catalog. However, there is no explicit guidance about when to prefer this over alternatives like ni_store_order (ordering) or ni_order_status (status), and no exclusions or prerequisites are mentioned. The verb 'Search' does imply the read-only use case, but not enough for a 4.

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