skillgild_search_skills

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

With no annotations, the description carries the disclosure burden and does well: it lists returned public metadata, access tier, version, and input schema, and explicitly says private prompts or implementation are never returned. It also explains the open-source distribution behavior, though it does not cover pagination, limits, or auth expectations.

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 first sentence front-loads the purpose, followed by return/privacy information and then the open-source caveat. All three sentences earn their place and there is no wasted preamble.

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 a one-parameter search tool with no output schema, the description explains what is returned and what is deliberately not returned. The additional open-source distribution nuance gives the agent enough context to interpret results correctly.

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 100%, so the schema already documents the single query parameter. The description adds no additional query semantics, format guidance, or clarification that the schema marks query required while its property text says optional, so baseline 3 is appropriate.

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 SkillGild's public skill catalog. The scope is clear and distinct from session/call/run siblings, so an agent can identify it 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?

Explains that open-source results install from source with `skillgild install <slug>` and do not run on SkillGild, which is important usage context. It stops short of naming when to use this versus `skillgild_run_skill` or `skillgild_call_tool`, so it is clear but not fully directive.

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