strata_list_skills

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

No annotations are provided, so the description carries the disclosure burden. 'List' implies a read-only operation and the description names the output fields, but it does not state scope details or behavioral caveats beyond that. For a simple zero-parameter list tool this is adequate, though minimal.

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 front-loaded sentence that states the action, the resource, and the relevant output attributes with no filler or 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?

For a zero-parameter list tool with an output schema, the description provides sufficient context: it names the operation, the resource, and the fields an agent can expect. No additional guidance is necessary to invoke it correctly.

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 properties are empty, so parameter semantics are not a concern. The description's field list refers to the output, not inputs, which is fine because there is nothing for the agent to configure.

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 verb and resource: 'List available skills' and enumerates the returned attributes (name, domain, mode, complexity, trigger). It is easily distinguishable from siblings by its plural 'skills' and list semantics, though it does not explicitly contrast with the singular 'strata_skill' tool.

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?

Usage is implied: an agent would call this when it needs a catalog of available skills. However, there is no explicit when-or-when-not guidance, and the sibling 'strata_skill' suggests an alternative that is not mentioned or routed around.

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