list_skills

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

With no annotations provided, the description carries the full burden. It discloses the private, model-specific nature of the data and the intended session-start usage. However, it does not explicitly affirm read-only behavior (though listing implies it), so a slight deduction.

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 three concise sentences: function, usage guidance, and scope limitation. Each sentence serves a distinct purpose, with the core action front-loaded.

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 simple zero-parameter list tool, the description provides purpose, usage timing, and data scope. It also references the companion tool list_strategies to clarify relationship. Return format isn't needed 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?

The tool has zero parameters and the schema covers 100% (empty). The description adds context about the content being listed but needs no parameter semantics.

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 lists the model's own previously written rules/skills, with an explicit scope of 'your own private file only.' This distinguishes it from sibling tools like list_strategies (which likely lists strategies) and get_skill/save_skill.

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 explicitly instructs to read this at the START of every session alongside list_strategies, providing a clear usage trigger. It also clarifies that it never shows another model's skills, preventing misuse.

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