yaaif_skill_enable

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It reveals that the tool flips the enabled state of a skill, but it does not mention persistence, side effects, permission needs, or whether a reload is required afterward.

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 sentence with no filler, front-loading the action. It is appropriately short for a simple toggle operation, though it is terse enough that some necessary context is missing.

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?

This is a 3-parameter mutation with no annotations and no output schema, so more context is needed. The description does not explain what 'skill_configs' refers to, how enabled maps to the boolean parameter, or whether updated_by is required. It is minimally usable but incomplete.

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. It adds some meaning by implying skill_id relates to 'a skill' and that enabled controls the 'enable or disable' action, but it does not mention the optional updated_by parameter at all. This is only partial compensation.

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 states a clear action ('Enable or disable') and a resource ('a skill in skill_configs'), so an agent can tell what the tool does. It does not explicitly differentiate this from sibling skill tools like yaaif_skill_refresh or yaaif_skill_runtime_reload, but the core purpose is unambiguous.

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 related skill-management tools such as yaaif_skill_validate, yaaif_skill_refresh, or yaaif_skill_update_module_files. There is no mention of prerequisites, alternatives, or exclusions.

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