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

Annotations already establish the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real signal beyond them: results are revision-pinned ("preserve exact Git revision") and carry maturity, status, and evidence labels, which tells the agent the output is provenance-tagged rather than free text. It says nothing about catalog freshness, rate limits, or cost, but the essentials are covered.

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?

Three sentences, correctly front-loaded with the usage condition before the catalog scope. The middle enumeration is long but is doing real work describing coverage breadth. Slight waste in "free shared agent-knowledge catalog" restating what the name already conveys.

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?

With an output schema present, the description needn't explain return values, and the when-to-use guidance plus provenance note is adequate for a search tool. But three of five parameters are enums with zero schema documentation and no description coverage, which is a meaningful gap for a tool whose main difficulty is choosing filters.

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% across 5 parameters, so the description must carry the burden and largely does not. It loosely gestures at the domain filter ("skills, guides, tools, code, patterns, research, and reference") but the list mismatches the enum — "tools" is not a value and "ecosystem" and "reviews" are omitted — and it mentions maturity/status only in the context of returned fields, not as filter inputs. The meaning of query, max_results, and the enum values themselves is left entirely unexplained.

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?

A concrete verb plus resource: "Search the free shared agent-knowledge catalog across skills, guides, tools, code, patterns, research, and reference material." An agent immediately knows this is a read against a shared/public catalog. It does not, however, distinguish itself from private_knowledge_search or community_get, which an agent seeing this sibling list would want.

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?

"Use when relevant shared methods, skills or evidence could help research, build or debug a task" gives an explicit triggering condition, which is more than most definitions offer. It stops short of exclusions or naming an alternative (e.g., use community_get once you already know the artifact id, or private_knowledge_search for internal material).

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