yaaif_desktop_skill_mapping_delete

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

No annotations are present, so the description must carry the burden of behavioral disclosure. It only says 'Delete', which implies destructive action, but does not disclose side effects, reversibility, error behavior on missing skill_id, or permission requirements. This is a significant gap for a mutation tool.

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, focused sentence with no fluff. It is appropriately sized for a simple delete operation, though it omits necessary context. Conciseness itself is good, but the content is too sparse.

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 single-parameter delete tool with no annotations, output schema, or parameter description, the description is incomplete. It fails to explain effects on worker mappings, any prerequisites, or expected results. An agent could call it incorrectly without knowing whether the mapping must exist or what happens on failure.

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 0%, so the description must compensate by explaining the parameter. It only repeats the parameter name ('skill id') without adding any meaning, format, or constraints. The description adds no value beyond the schema's property name.

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 action (Delete) and the resource (desktop worker↔skill mapping) and specifies it's for a skill id. It is specific enough to distinguish from list and set operations, though it doesn't explicitly name alternatives.

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 gives no guidance on when to use this tool, what constitutes a prerequisite (e.g., existing mapping), or how it relates to sibling operations like yaaif_desktop_skill_mapping_set or yaaif_desktop_skill_mappings_list. No when/when-not guidance is provided.

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