搜索技能市场

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

No annotations are provided, so the description carries the burden. It discloses the prerequisite of loading the SKILL and clarifies that installation happens separately via capability_run, implying the search itself is read-only. It does not detail pagination or auth, but the core behavioral context is present.

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 description is compact: two sentences covering prerequisite, search location, and installation next step. It is front-loaded and every sentence contributes value, though the dense phrasing slightly reduces readability.

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 only one simple parameter and no output schema, this is a straightforward search tool. The description covers the prerequisite, the search scope, and the downstream install action, making it reasonably complete for an agent to invoke correctly. It could mention return format, but that is not critical here.

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 has 100% coverage with a description and examples for the single keyword parameter. The description only echoes the same example categories without adding new param-specific meaning, so it stays at the baseline.

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 tool searches the HarmonyOS skills marketplace (matrix.openharmony.cn) for expert skill packs, using specific verbs and resource. It differentiates from sibling tools like docs_search and capability_search by targeting the skills marketplace specifically, and mentions the follow-up install via capability_run.

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?

It provides clear workflow context by requiring the deveco-unified-mcp SKILL to be loaded first, and tells the agent to use capability_run's skills.add to install after finding. It does not explicitly list when not to use it, but the practical guidance is sufficient.

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