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

Annotations already flag this as non-read-only and destructive. The description importantly clarifies that delete removes the saved view but 'the records stay,' which prevents a serious misinterpretation of destructiveHint. It does not discuss idempotency or permissions, but with annotations covering the safety profile this is solid added context.

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?

The description is extremely compact and front-loads the resource definition before breaking down each action. Every phrase carries useful information, including the key deletion clarification.

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 five-parameter manage tool with no output schema, the description covers the action set, filterJson creation guidance, and delete semantics adequately. It omits any explanation of entityType, which is the main remaining contextual gap.

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 60%, and the description helps with filterJson by telling the agent to copy its shape from saved_views_list. It does not explain entityType, and id/name requirements are left to the schema. Baseline 3 is appropriate given partial schema coverage and only marginal extra parameter guidance.

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 names the resource as saved views (named filters) and enumerates the managed actions create, update, and delete. It also references saved_views_list for filter shape, but it does not explicitly draw the full boundary between managing views and listing them.

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?

It gives action-specific hints such as 'rename or change the filter' for update and 'copy filterJson's shape from saved_views_list' for create. However, it does not explicitly state when to choose this tool over saved_views_list or explain prerequisites for each action, leaving usage mostly implied by the action enum.

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