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

Annotations already declare readOnlyHint=true. The description adds useful behavioral context by stating that results contain only contextual snippets and that the underlying content is public and Aident-curated. This helps the agent know what to expect before calling skills_read.

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?

Two concise sentences with no filler. The action and resource are front-loaded, and the second sentence earns its place by routing the agent to the complementary skills_read tool.

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?

The workflow is clearly stated, but a 7-parameter search tool with no output schema and low schema description coverage needs more detail about filter semantics or result shape. The description is adequate for a first search, but it leaves optional parameters unexplained.

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 only 14% across 7 parameters, and the description does not explain any parameter beyond implying that query is the search text. Sort, tags, limit, cursor, category, and referencedCapabilityNames must be inferred from their names and types, which is insufficient.

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 Aident-curated public text Skills.' It also distinguishes itself from skills_read by directing the agent to call skills_read to load full entrypoints. The scope (public, curated) makes the tool's purpose immediately clear.

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?

Gives a clear workflow: use skills_search to get snippets, then call skills_read to pick a result and load full content. It does not cover when skills_search is unnecessary, such as when a specific skill ID is already known, so the guidance is useful but not exhaustive.

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