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

Annotations declare destructiveHint=true and idempotentHint=false for what reads as a benign 'save', but the description never explains the overwrite/destructive semantics or retry behavior. The note that known case filters are normalized by the same service as the UI is genuinely useful added context, but it is the only behavioral disclosure.

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 with the core action front-loaded and no filler. The normalization sentence is slightly oblique but does convey a real behavioral fact.

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 7-parameter destructive mutation with near-zero schema documentation and no output schema, the description leaves far too much unexplained: what `id` means, whether `company` scopes the view, and what happens on name collision. It is well short of what an agent needs to call this safely.

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 only 14% (just idempotency_key), so the description must carry the burden; it only implies the `shared` flag ('personal or shared') and adds meaning to `query` via filter normalization. Six required parameters including `company`, `id`, `kind`, and `name` get no explanation at all.

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?

States a specific verb ('Save') and resource ('personal or shared inbox view'), which lets an agent distinguish it from summer_saved_views_list and summer_saved_views_delete. It does not, however, say how it relates to those siblings (e.g., whether saving with an existing id updates rather than creates).

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 never states when to use this tool versus saved_views_list/delete, nor any prerequisite such as needing an existing view id or an idempotency key for retries. The second sentence is behavioral trivia, not usage guidance.

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