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

Discloses embedding via Cloudflare Workers AI, cosine distance retrieval, and threshold logic. Annotations already indicate readOnlyHint=true, so the description adds algorithmic context without contradiction.

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: purpose, mechanism, usage. Front-loaded and efficient, no extraneous 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?

Covers purpose and algorithm, but missing return format (e.g., list of skill objects with distances) and error handling. Given no output schema, the description should at least mention what the tool returns.

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?

With 0% schema description coverage, the description must add parameter meaning. It explains 'query' as candidate goal text and 'k' as number of closest skills, but lacks format guidance or examples, leaving semantic gaps.

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 retrieves skills by description similarity using Voyager. It uses specific verbs like 'retrieval', 'embeds', and 'closest', and distinguishes from siblings like list_my_skills (listing all) and invoke_skill (execution).

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?

Provides explicit decision rule: invoke first match if distance < 0.25, else generate new actions. This guides when to use the tool's output, though it doesn't compare directly to alternatives like list_my_skills or invoke_skill.

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