list_badge_skills

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

With no annotations, the description carries full burden. It only states the basic function and optional filter. It does not disclose any behavioral traits such as pagination, ordering, error handling, or response structure beyond what is implied by a list operation.

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 immediately states the purpose and optional filter. No unnecessary words or fluff.

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 optional param) and presence of an output schema, the description is mostly complete. It covers purpose and filtering context. However, it omits trivial behavioral notes like ordering or whether an empty list is returned for no skills.

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 100% for the single parameter, and the description echoes the optional filter nature. However, it adds no new semantic meaning beyond what the schema already provides, such as data type or source of resume_id.

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 'List', the resource 'badge skills', and defines the scope as including technologies, tools, and languages. It distinguishes from siblings like 'get_badge_skill' (singular) and other list tools.

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 usage for listing all skills or filtering by resume, but does not explicitly state when to use this tool vs alternatives like 'get_badge_skill' or when not to use it. It provides context via the resume_id parameter but lacks explicit guidance.

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