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

Annotations already establish a safe read (readOnlyHint=true) and closed-world scope (openWorldHint=false), and the description reinforces the latter with 'reads our catalog without calling listed servers.' It adds real behavioral detail beyond annotations: AND-combination of filters, the no-match rule for capabilities, and alphabetical ordering.

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 densely packed sentence front-loads the purpose, then enumerates filters and behavioral rules. It is efficient with no filler, though the run-on enumeration of parameters is slightly heavy.

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 an eight-param, no-output-schema search tool, the description covers filter semantics, ordering, and the non-invasive read behavior. It leans on an external API reference ('same response as GET /api/v1/mcp-servers') rather than describing the return shape directly, which is a minor gap.

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 0%, so the description carries the burden, and it does list all eight params with q's 80-char cap and the limit/offset bounds plus filter-combination semantics. However, most of these constraints and the enum values already live in the schema, so it adds only marginal interpretation beyond the structured fields.

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 concrete verb (search) and a precisely scoped resource (the reviewed MCP directory), which cleanly separates it from siblings like get_mcp_server (single fetch), search_providers, and search_tools. An agent can identify the target corpus without opening 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 description implies usage (search the reviewed directory) and clarifies it reads the catalog without calling listed servers, but it never states when to prefer this over search_providers/search_tools or get_mcp_server. No explicit alternatives or exclusions are given.

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