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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the description does not need to repeat safety claims. It adds value by disclosing that the result includes input schemas and working example inputs and that category is an optional filter.

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, front-loaded sentence that moves from action and scope to output contents to optional filtering. Every phrase earns its place and nothing is wasted.

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 simple, read-only listing tool with one optional parameter and no output schema, the description supplies enough to call it correctly: what is returned, how to narrow results, and the fact it is scoped to run_tool. No critical detail is missing.

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 schema already documents the single category parameter with 100% coverage ('Optional category slug'). The description adds that category acts as a filter, which is minor given the schema carried almost all of the semantic weight; no format or allowed values are given.

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 action ('List') with a well-defined resource: every ToolsMonk tool that run_tool can execute, and further specifies the returned content (input schema and working example). This scope distinguishes it from siblings like list_tools and get_tool without needing to open the schema.

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 purpose wording makes clear this is the right tool when an agent needs the runnable subset of ToolsMonk tools with runnable examples, rather than all tools or a single tool. It does not explicitly name list_tools as the alternative or state when not to use it, so it falls short of a full 5.

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