Summarize a tool or category

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

The description adds significant behavioral context that is not covered by the annotations or schema. It defines the granularity of the output (a summary, maximum of three examples), the level of specificity required for the query (exact name/slug), and the data limitations (no full records, no pagination).

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 definition is extremely concise. Both sentences are highly information-dense and functional. The constraints and limitations are front-loaded, making the entire definition efficient and easy to digest.

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 its simplicity and the coverage provided by the annotations (read-only, closed world), the description is highly complete for the intended use case. It clearly defines the scope and boundaries of the tool.

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 coverage is 100%, establishing a baseline of 3. The description does add useful semantic meaning by clarifying that 'query' requires an 'Exact tool name or slug,' which helps the agent understand the constraint applied to that parameter beyond its basic type definition.

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 function: to summarize tool names or categories. It defines two specific usage modes: querying an 'exact tool name or slug,' or retrieving 'up to three examples from a specific category.' This is specific, but the name 'list_tools' is slightly broad for the act of 'summarizing,' preventing a score of 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?

The description provides excellent boundaries for usage by explicitly stating what the tool will NOT do: 'No bulk exports, pagination or full records.' This sets clear expectations and steers users away from incorrect use cases (e.g., attempting to dump a database).

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