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

No annotations are provided, so the description must disclose behavior on its own. It only states that skills are technical and professional; it does not describe the return format, ordering, filtering, or any other behavioral detail. The 'list' verb in the title implies a read operation, but the description adds no transparency.

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 terse, but it is under-specified to the point of being a fragment rather than a well-structured instruction. It lacks an explicit verb and conveys only the subject matter, not the operation or output.

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 parameterless list tool the scope is small, but with no output schema and no annotations, the description should at least clarify what the returned skills list contains. The brief phrase does not fully equip an agent to know what to expect from the tool.

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, so the baseline is 4. The empty schema fully defines parameter expectations, and there is nothing for the description to add about individual parameters.

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 title and name both include 'list' and 'skills', and the description identifies the resource as 'technical and professional skills'. However, the description itself is a noun phrase rather than a statement of what the tool does, and it does not differentiate the tool from siblings beyond naming a distinct resource.

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 is provided about when to use this tool versus alternatives such as list_projects or query_profile. There is no mention of use cases, context, or exclusions, leaving the agent to infer when skills are needed.

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