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

With no annotations, the description carries the full burden, yet it only states the 50-per-page cap, which the schema already enforces via page_size maximum=50. It omits the default page size, whether page numbering is 0- or 1-based, whether a total result count is returned, and any permission or rate-limit behavior.

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?

A single tightly packed sentence that front-loads the resource and folds scope, filtering, sorting, and the page-size cap into one clause with no filler.

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 5-parameter paginated list tool with no output schema, the description should clarify pagination defaults and the relationship to search/filter. It covers the browse surface adequately but leaves the agent guessing about defaults and how results are returned.

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 only 40% across 5 parameters, so the description must compensate. It does add useful meaning for category (path or name), the stock-only flag, and sorting direction, but page and page_size semantics (defaults, numbering, behavior at the boundary) remain undocumented in both places.

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 gives a specific verb (browse/list) and resource (Media Depot's products) and adds scope modifiers: category filtering, stock filtering, sorting, and page size. It is clear what the tool does, but it never distinguishes itself from siblings like search, filter, or product, which an agent could easily confuse with browsing a catalog.

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?

There is no explicit guidance on when to use browse versus search, filter, categories, or product. The optional category parameter hints at a browsing use case, but the agent must infer the boundary itself, and no exclusions or prerequisites are stated.

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