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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond them: the tool is a local catalog lookup that does not hit the Convocore backend, and the detail knob governs response verbosity. Return shape is only implied.

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 short sentences, zero filler, with the purpose and the pre-call routing instruction front-loaded before the parameter hints. Every sentence contributes distinct information.

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 no output schema, the description's detail=names|brief|schema line does the job of telling the agent what comes back at each verbosity. The undisclosed 'limit' parameter and missing default for detail are the only residual gaps for a 4-parameter meta 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?

Schema description coverage is 0%, so the description must carry the load and largely does: it explains that query is keyword/domain-based, that domain draws from the enumerated set, and that detail selects names|brief|schema payload depth. Only 'limit' is left entirely undocumented.

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 verb and resource ('Search this MCP server's tool catalog by keyword/domain') and enumerates the domain space it covers (orgs/clients/leads/agent_tools/variables/kb/testing), which makes it instantly distinguishable from every domain sibling. It stops short of a perfect 5 only because the phrase 'tool catalog' is the sole framing of scope.

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?

Explicitly says to use it 'before calling other tools' and 'when unsure which tool to pick', which is a concrete triggering condition. The closing sentence 'Does not call the Convocore API' rules out the common misread that this is a data-query tool. No explicit when-not beyond that, so not a 5.

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