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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by spelling out the return shape in both modes (category list with counts/tags, exhibit list with id, title, broken assumption, tags, and repro languages) — important because there is no output schema.

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?

Two compact sentences, each doing distinct work: the first states the tool and the no-arg behavior, the second states the filtered behavior and output fields. Front-loaded and free of 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 two-optional-param discovery tool with no output schema, the description covers both input modes and the returned fields, which is what an agent needs to call it and interpret results. It lacks sibling routing guidance and any note on result limits, but the core is complete.

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 100%: both parameters carry descriptions and the category enum is fully enumerated. The description's enumeration of categories and its note about 'most common tags' mildly reinforces this but adds no syntax or precedence guidance (e.g. what happens if both tag and category are supplied). Baseline 3 is appropriate.

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 names a concrete verb and resource ('browse the collection') and immediately enumerates the eight categories and the fields returned, so an agent knows exactly what it gets. It does not explicitly distinguish itself from siblings like edge_case_get or edge_cases_find, which is the only thing keeping it from a 5.

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?

It clearly describes the two invocation modes ('With no arguments...' vs 'With category or tag...'), which is useful usage context. However, it never says when to prefer this over edge_cases_find or edge_case_get — the agent must infer that browse is for discovering what exists and get/find is for retrieving a specific item.

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