review_queue

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

With no annotations, the description must disclose behavior itself, but it only describes the queue's contents, not what the tool does when invoked. It is unclear whether this is a read-only list or if it triggers any side effects, such as marking items as reviewed.

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, focused sentence with no unnecessary words. It clearly communicates the key content of the queue in a front-loaded manner.

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?

Given the absence of annotations, output schema, and parameters, the description is too thin. It tells the user what the queue contains but not what the tool does, what it returns, or when to use it, leaving an agent with insufficient detail to invoke it confidently.

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?

There are zero parameters, so no parameter explanation is needed. The description adds no parameter-specific information, but this is not a gap since the schema covers everything (empty properties). Baseline 4 applies.

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 identifies the resource (categorization review queue) and specifies its contents (uncategorized merchants + individual checks), which distinguishes it from siblings. However, it lacks an explicit verb like 'lists' or 'shows', so it reads more like a definition than an action.

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?

No guidance is provided on when to use this tool versus alternatives such as open_conflicts or set_merchant_category. There is no mention of context, prerequisites, or what makes this tool the preferred choice.

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