Run knowledge skill

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

With no annotations, the description must fully disclose behavioral traits, but it only says 'Run...' without mentioning whether the operation is synchronous, requires prior configuration, has side effects, or returns a result. No behavioral context is added beyond the most surface-level action.

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 redundancy or filler. It is front-loaded and easily scannable, though its brevity contributes to the incompleteness penalized elsewhere.

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 lack of annotations, output schema, and any parameter documentation, this description is not self-sufficient. It leaves out essential context such as how to obtain a valid skill, whether the selection must already exist, and what the return value or side effects are. Only the core intent is conveyed.

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 clarifies that selectionId is the target selection and skill is a 'configured knowledge processing skill', but it says nothing about chunkSize, nor does it explain the relationship or expected format of skill values. The compensation is minimal.

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 ('Run') and the resource ('configured knowledge processing skill') against a 'selectionId'. This is more specific than a mere restatement of the title, though it doesn't explicitly contrast with siblings like baidu_analyze_selection, so it isn't a 5.

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?

There is no guidance on when to use this tool versus alternatives such as baidu_list_skills, baidu_analyze_selection, or baidu_plan_organize_selection. The description implies a generic execution action but provides no prerequisites, exclusions, or selection criteria.

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