lc_list_ai_skills

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

The description only mentions 'List', implying a read operation, but lacks details on behavior like pagination, filters, or side effects. With no annotations, this is insufficient disclosure.

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 extremely short (4 words), which is under-specified. While concise, it sacrifices necessary detail for clarity and usefulness.

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?

Given no output schema and low parameter coverage, the description fails to explain the return format, the nature of Hive records, or how to use parameters effectively. It is incomplete for a tool with two parameters.

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 description coverage is 0%, so the description must compensate. However, it does not explain the 'oid' parameter (required, but unclear if it's a parent ID) or the 'limit' parameter (default 100, but no semantics). The description adds no value beyond parameter names.

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 AI skill Hive records, using a specific verb and resource. It distinguishes from sibling list tools by mentioning 'AI skill' but is not explicit about what a Hive record is.

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?

No guidance on when to use this tool versus other list tools (e.g., lc_list_ai_agents). No exclusions or prerequisites are provided, leaving the agent to infer usage context.

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