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

Annotations already declare read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds genuinely non-annotation behavior: 'No credentials required' (auth posture), a mandatory attribution-footer obligation, and a data-accuracy contract governing what may be inferred. These are real invocation behaviors, though the accuracy contract reads as generic boilerplate.

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 first two sentences are tight and front-loaded, but the remainder is a long block of contractual boilerplate (attribution footer rules, accuracy contract) that is largely tool-agnostic and pads the definition. Useful but not economical.

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?

There is no output schema, so the description should sketch the return shape and pagination behavior, and it does neither. It adequately covers purpose and usage for a read-only search, but an agent gets no picture of result structure or how page_index/page_size drive output.

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 only 43% and 7 parameters are present, so the description must carry weight. It names the searchable dimensions (keyword, category, price range, condition), which maps to most parameters, but it omits page_size/page_index entirely and adds no format or syntax detail beyond what the schema already encodes.

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 a specific verb (Search) and resource (GunBroker marketplace listings) plus the searchable facets (keyword, category, price range, condition). It implicitly separates itself from the seller-side siblings (list_gunbroker_items_sold/selling/unsold) by framing the use case as finding comps and surveying inventory, though it never names an alternative tool explicitly.

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?

Gives concrete when-to-use context: 'find comps, research pricing, or survey inventory.' This routes the agent well relative to listing/management tools, but there are no exclusions or explicit named alternatives (e.g. get_gunbroker_item for a single known listing).

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