list_skills

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'list skills with optional category filter' and does not mention pagination, sorting, return format, or whether the list is complete or partial. The schema includes limit/offset but their presence is not explained.

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 with no unnecessary words, making it easy for an agent to quickly parse its purpose.

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 simple listing tool, the description is minimal but adequate for understanding the core action. However, it lacks details about pagination controls (limit/offset) and doesn't clarify how it differs from search_skills, leaving gaps in completeness given the absence of annotations and output schema.

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 coverage is only 33% (category alone has a description); limit and offset have no descriptions. The tool description adds no new meaning for these parameters and merely echoes 'optional category filter', which is already present in the schema. It does not compensate for the undocumented 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 description clearly states the tool's function with the verb 'List' and resource 'skills', and mentions the optional 'category filter', which differentiates it from sibling tools like get_skill (specific skill retrieval) and search_skills (keyword search).

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 implies a general listing use case with optional filtering, but it does not explicitly state when to prefer this over search_skills or get_categories, nor does it mention any exclusions or alternatives.

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