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

Annotations already declare mutation (readOnlyHint=false), non-destructive, and non-idempotent, so the safety profile is covered. The description adds genuinely new behavioral information the annotations do not carry: merge-vs-clear semantics for omitted fields versus explicit null. It stops short of stating what is returned or what permissions are needed.

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 sentences, zero filler. The capability list comes first and the partial-update rule second, which is the right ordering for an agent that needs to know what it can change before how.

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 15-parameter mutation tool with no output schema, the description covers the two things that matter most: which fields are settable and how omitted/null values behave. Gaps remain around return value, permissions, and validation constraints (e.g. the maxItems limits on sort/filter), but the schema itself carries most of that.

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 coverage is only 47%, so the description has to compensate, and it does at the category level: it names the name/filter/sort/hiddenFields families and flags that further settings are view-type specific (which maps to groupBy, dateField, laneField, coverField, timelineScale). The 'null clears one' sentence is the key semantic that the anyOf-null schemas do not spell out; only calendarMode and timelineScale remain unexplained in both places.

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?

Uses specific verbs (rename, change) against a specific resource (view) and enumerates the mutable facets: filter, sort, hidden fields, type-specific settings. An agent can distinguish it from create_view or update_table without opening the schema, though no sibling is named explicitly.

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 wording implies this operates on an existing view (as opposed to create_view), and the 'settings you leave out are kept' clause implicitly scopes it to partial edits. However, there is no explicit when-to-use/when-not statement, no mention of alternatives, and no prerequisite guidance such as required permissions or which view types accept which settings.

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