gsa_set_view_labels

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

No annotations are provided, so the description carries the full burden. 'Apply' implies a mutation of the view, but the description does not say whether existing label settings are overwritten, whether the GWA record must exist first, whether permissions are required, or what happens on failure.

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?

It is a single short sentence with no wasted words, which is structurally fine, but the brevity comes at the cost of under-specification rather than tight editing of a complete thought.

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?

An output schema exists so return values need not be described, but for a mutation tool with zero annotations and 0% schema description coverage, the description is far too thin to let an agent invoke it confidently.

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% and neither parameter is documented in the schema. The description only obliquely gestures at saved_view_gwa ('template GWA record') and says nothing about view_id, leaving the agent to guess the relationship between the ID and the template.

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 gives a verb+resource ('Apply label settings') and hints at the source ('from template GWA record'), which loosely distinguishes it from siblings like gsa_set_view_base_settings or gsa_set_view_contour. However, 'GWA record' is unexplained jargon and it never clarifies what a 'view label' is or how this differs from the other view-setting tools in the family.

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 gsa_set_view_base_settings, gsa_set_view_contour, gsa_set_view_diagram, or gsa_update_views. The agent must infer usage purely from the name, and no prerequisites or preconditions are stated.

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