invariance_saved_view_create

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

The annotations already indicate readOnlyHint=false and destructiveHint=false, and the description's 'Create' is consistent with that. However, the description adds no behavioral context beyond the basic write action, such as whether the view is immediately persisted, requires a unique name, or has side effects.

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 a single, front-loaded sentence with no filler. It efficiently communicates the core operation and scope.

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?

With five parameters, no output schema, and limited annotations, the description is too sparse for an agent to confidently invoke the tool. It omits what a saved view is for, how visibility works, what the spec must contain, and what the result of creation is.

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?

The description does little to explain the parameters beyond indicating that the view is 'over executions/events/runs/nodes/captures', which maps to the source enum. Schema description coverage is only 20%, and while the spec property has a detailed schema description, the tool description itself does not clarify name, viz, visibility, or how they interact.

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 a specific verb ('Create'), a concrete resource ('saved query view'), and the valid data sources. It clearly conveys the tool's purpose, though it does not explicitly differentiate itself from the related saved_view_get/list/update/run/delete siblings beyond the verb.

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?

No explicit guidance is given for when to use this tool versus alternatives. There is no mention that this is for creating a new view rather than updating, running, or listing views, so an agent must infer usage from the name and description.

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