Edit top skills

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

With no annotations, the description carries the full burden. It does disclose the dry_run default and login requirement, which are key behaviors. However, it leaves the exact semantics of replace vs merge and the role of remove_ids/remove_names unspecified, and there is no annotation to fill these gaps.

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, well-structured sentence. It front-loads the action, includes the maximum count and rating levels, and ends with the critical dry_run default. No filler or redundant phrasing.

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 5-parameter tool with no output schema and no annotations, this description is too thin. The two removal parameters (remove_ids, remove_names) are completely unexplained, and the merge/replace distinction is not elaborated enough for an agent to safely invoke the tool without guessing.

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 only 40%, so the description should compensate. It clarifies the mode and dry_run behavior, but it mostly repeats the enum and maxItems already present in the schema. It says nothing about remove_ids or remove_names, leaving two parameters effectively undocumented.

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 specific operation ('Replace or merge') on a specific resource ('WAAS top skills') with clear constraints (max 10, rating levels). This clearly distinguishes it from siblings like waas_edit_share and waas_update_profile, which target different aspects of the profile.

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?

It provides some usage context by naming the two modes (replace vs merge) and the default dry_run=true behavior, but it does not explicitly state when to prefer this tool over alternatives or mention exclusions. The intended usage is implied from the purpose, not explicitly routed.

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