linear_createSavedView

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

Annotations indicate readOnlyHint=false, so agents know it's a mutation. However, the description adds no details about side effects, uniqueness constraints, or behavior on duplicate names. No contradiction with annotations, but insufficient for a full behavioral picture.

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 sentence that is front-loaded with the essential purpose. It is concise with no superfluous content, though it could include a brief hint about the API name being secondary.

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?

Given the 11 parameters, many of which are complex objects (filters, filterData), the description does not explain how to use them or provide examples. The presence of an output schema is noted but not leveraged in the description. The tool feels under-documented for its complexity.

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 100%, so the baseline is 3. The description does not augment parameter information; it simply repeats the tool's purpose. No additional meaning is provided beyond what the schema already offers.

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 clearly states the verb 'Create' and the resource 'Linear saved view', with an API name reference. It distinctly separates this tool from sibling tools like linear_getSavedViews, linear_updateSavedView, and linear_deleteSavedView.

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 provides no guidance on when to use this tool versus alternatives, such as when creating a saved view is appropriate compared to using issue filters or other customization tools. It lacks any context for decision-making.

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