labels_enable

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

With no annotations, the description transparently reveals that the tool applies simple (non-rule-based) labeling and uses default text formatting. It does not cover potential side effects on existing labeling but is otherwise informative.

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?

Two short sentences efficiently convey purpose, constraints, and next steps with no redundancy. Front-loaded with the main action.

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 simple tool with three parameters and an output schema, the description adequately covers the essentials: what it does, how to use parameters, and what to do next. Minor omission about handling existing labeling does not significantly detract.

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?

Although the schema has no descriptions (0% coverage), the description clarifies that field and expression are exclusive alternatives for the labeling source, adding meaning beyond the raw schema. The required layer_id is implied but not explicitly described.

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 tool enables labeling for a vector layer, specifying the source as a field or expression. It distinguishes from sibling tools like labels_configure and labels_disable by mentioning the next step after enabling.

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 instructs to pass exactly one of field or expression, and indicates that this applies simple labeling with default settings, directing users to labels_configure for further adjustments. This provides clear when and when-not usage.

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