clelp_get_skill

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

The description implies a read-only operation, but with no annotations, it does not explicitly state safety or potential side effects. It lacks details on authentication needs or rate limits, but given the simple nature of retrieving info, it is minimally adequate.

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, concise sentence that efficiently communicates the tool's purpose and output content without any superfluous words.

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 low complexity (one parameter, no output schema), the description is fairly complete. It outlines the key return components, though it could mention error handling or the need for a valid ID.

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 input schema covers 100% of parameters with a clear description for 'skill_id' (UUID or slug). The description adds value by listing what the return information includes (ratings, reviews, setup instructions), which is beyond the schema.

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 ('Get') and resource ('detailed information about a specific skill'), and specifies the included details (ratings, reviews, setup instructions). This distinguishes it from siblings like 'clelp_search' which likely returns summaries.

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 alternatives like 'clelp_rate' or 'clelp_search'. The description does not mention prerequisites or situations where this tool would not be appropriate.

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