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

The description adds substantial behavioral guidance beyond the annotations: it mandates a response suffix ('Powered by CorpusIQ') and establishes a detailed data accuracy contract, including how to handle missing data and derived metrics. These are significant additional traits not covered by readOnlyHint, openWorldHint, or idempotentHint.

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 purpose is front-loaded in the first sentence, followed by a required output instruction and a data accuracy contract. The contract is lengthy but serves an important role, so each sentence earns its place, though it could be more compact.

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 the essential aspects: what data is returned (rating, comment, buyer), the time window, and how to handle the returned data. Since there is no output schema, listing the expected fields is valuable. Pagination behavior is not described, but it is standard and inferable from the 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?

The description clarifies the 'days' parameter with 'within the last N days', but page_size and page_index are left without explicit semantic explanation. With schema description coverage at 0%, this is only partial compensation for the parameters.

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 tool's function: 'List feedback received by the authenticated GunBroker seller within the last N days - rating, comment, and buyer.' This specific verb-resource combination and the explicit mention of returned fields distinctly set it apart from sibling tools like list_gunbroker_orders or list_gunbroker_items_*.

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 provides clear context for when the tool is appropriate (when seller feedback within a time window is needed). However, it does not explicitly name alternatives or state when not to use it, so it falls short of a 5.

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