gsa_set_view_base_settings

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

No annotations are provided, so the description carries the full behavioral burden. It is a mutating operation ('Apply') applied to an existing view (view_id is required), but the description never states whether it overwrites existing settings, what template GWA actually means, whether it is reversible, or whether re-application replaces prior settings. This is a significant gap for a mutation with zero annotation coverage.

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?

A single short sentence with no wasted words, front-loaded with the verb. Brevity is good, though here it may reflect under-specification as much as efficiency.

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?

Jargon terms 'GWA' and 'base settings' are undefined, no annotations exist, and the parameters are undocumented. An output schema exists, so return values need not be explained, but everything else an agent needs to invoke this correctly is missing.

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% for both required parameters. 'view_id' is a fairly self-evident integer, but 'saved_view_gwa' is opaque jargon (a template identifier?) and the description does not clarify its format, source, or relationship to the view. With low coverage, the description must compensate and it does not.

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 says 'Apply base settings from template GWA record,' which at least names a verb ('Apply') and a resource ('base settings'), but 'GWA record' and 'view base settings' are undefined domain jargon. Among siblings like gsa_set_view_contour or gsa_set_view_labels, it isn't clear what distinguishes 'base settings' from those specific view settings.

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 versus alternatives. The sibling set contains several view-configuration tools (gsa_set_view_contour, gsa_set_view_labels, gsa_set_view_diagram) and update tools (gsa_update_views), but the description doesn't indicate when base-settings application is appropriate or what prerequisites exist.

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