yaaif_desktop_skill_mappings_list

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

No annotations are present, so the description carries the full burden. 'List' implies a read-only operation and 'control-plane' hints at management scope, but the description does not explicitly state side-effect freedom, whether results are filterable by skill_id, or what the response contains.

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 filler. Every word contributes to identifying the operation and its domain.

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?

The tool is simple, but the description leaves the optional skill_id filter entirely unexplained and provides no output or behavioral context. An agent can list all mappings with no arguments, but cannot correctly use the optional parameter or fully judge the tool's scope.

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 only parameter, skill_id, is completely undocumented in both the schema and the description. With 0% schema description coverage, the description needed to explain that this parameter filters mappings by skill, but it never mentions it.

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 uses a specific verb ('List') and a clear resource ('desktop worker↔skill mappings'), and the parenthetical 'control-plane' adds domain context. It is clearly distinct from sibling tools like yaaif_desktop_skill_mapping_set and yaaif_desktop_skill_mapping_delete.

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 given about when to use this tool versus alternatives such as yaaif_desktop_workers_list or yaaif_skill_map_agents. The word 'List' implies a read operation, but there is no explicit context, exclusions, or mention of related tools.

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