roiq_list_skills

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

The description does not disclose behavioral traits beyond being a list. Since no annotations are provided, the description should ideally state if it is read-only or safe. However, the nature of listing skills is inherently non-destructive, so a score of 3 is acceptable.

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 a single, clear sentence that immediately states the purpose. It is front-loaded with the action and resource, and every word is necessary.

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 tool with no parameters and no output schema, the description is complete. It tells the user exactly what the tool does and how it relates to another tool (roiq_run_skill). No further information is needed.

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?

There are no parameters in the input schema, and the schema description coverage is 100%. The description adds no parameter information, but none is needed. With zero parameters, baseline is 4, but it earns a 5 for clarity and conciseness.

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 all skills of the ROIQ OS engine that can be executed with roiq_run_skill. It uses specific verb 'list' and resource 'skills', and distinguishes itself from sibling tools that deal with other entities like cards, spaces, or pages.

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 implicitly guides usage by linking to roiq_run_skill, indicating this tool is a prerequisite. However, it does not explicitly state when not to use it or provide alternatives, but the context is sufficient for a simple listing tool.

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