lc_get_ai_skill

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

No annotations are provided, so the description must carry the burden. It only states the action without disclosing behavioral traits such as read-only nature, auth requirements, or side effects. The agent cannot infer safety or expected behavior.

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?

At only 5 words, the description is extremely concise but at the expense of necessary structure and information. It does not front-load key details or use formatting to aid comprehension. The brevity is harmful given the complexity of the tool.

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 the presence of 2 required parameters with no descriptions, no output schema, no annotations, and no sibling differentiation, the description is incomplete. It fails to inform the agent about what the tool returns or how to use it effectively.

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%, meaning the input schema provides no descriptions for the two required parameters (oid, name). The tool description does not explain these parameters, leaving the agent without semantic understanding of what values to provide.

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 'Fetch one AI skill Hive record' clearly states the action (fetch) and resource (one AI skill Hive record). It is specific and distinguishes from sibling tools like 'lc_list_ai_skills' and 'lc_get_ai_agent'.

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 provides no guidance on when to use this tool vs alternatives. It does not mention any prerequisites, context, or exclusions. Among many similar get tools, no differentiation is offered.

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