list_categories

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

With no annotations provided, the description carries the full burden of disclosure. It partially compensates by describing the return payload ('descriptions and skill counts'), but lacks information on caching, rate limits, authorization requirements, or pagination behavior for the 'all' scope.

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, efficient sentence that front-loads the action verb. Every clause earns its place by specifying scope ('all'), domain ('on SkillFlow'), and return structure ('with descriptions and skill counts').

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 tool's low complexity (no parameters, simple list operation) and lack of output schema, the description adequately covers the functional scope by clarifying the return data includes descriptions and counts. It appropriately conveys what the agent will receive without an explicit 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?

The tool has zero parameters, which per the rubric establishes a baseline score of 4. The description does not need to compensate for missing schema documentation.

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 provides a clear verb ('List') and specific resource ('skill categories on SkillFlow'), and clarifies what data is returned ('descriptions and skill counts'). However, it does not explicitly differentiate from siblings like search_skills or get_skill_details via comparison, only implicitly through the resource name.

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 contains no guidance on when to use this tool versus alternatives such as search_skills, nor does it mention prerequisites or exclusions. It states what the tool does but not when it should be selected.

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