store_skill

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

With no annotations, the description fully handles behavioral context. It states the side effect ('persists a new skill entry and indexes it') and crucially notes 'RecallNest does NOT execute skills — implementation is a runbook agents read as context,' preventing misuse.

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 concise at four sentences, front-loaded with purpose and side effect, then usage and critical caveat. Every sentence earns its place with no redundancy.

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?

Considering 10 parameters, 6 required, no output schema, the description adequately covers purpose, side effects, usage, and behavioral nuance. It lacks return value details, but those are not expected without an output schema.

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 coverage is 100%, so baseline is 3. The description adds some value (e.g., explaining 'description' is for retrieval matching, 'triggerPattern' is a natural language pattern), but most parameter meanings are clear from the schema.

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 'Store an agent-readable skill runbook with trigger conditions, instruction content, and verification steps.' It specifies the verb (store), resource (skill runbook), and key attributes, distinguishing it from sibling tools like 'retrieve_skill' or 'store_workflow_pattern'.

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?

The description explicitly says 'Use when you identify a reusable procedure worth surfacing across sessions.' It provides a clear usage context but does not explicitly exclude alternatives or state when not to use, though the intent is clear.

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