List saved dashboard filters

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description carries a lighter burden, but it adds almost no behavioral context beyond restating that it's a list operation and giving the REST path. It says nothing about what a saved view contains, whether results are paginated, or how omitted filters affect the result set.

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?

One front-loaded sentence with no filler; the parenthetical endpoint is mildly redundant but cheap and informative. Its terseness is efficient rather than padded, though it verges on under-specification for the schema it fronts.

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?

This is a simple read-only list tool, but with no output schema and no parameter documentation, an agent still cannot tell what is returned (ids, names, filter payloads?) or how the kind filter behaves. The definition is complete enough to call, but not complete enough to call correctly or to use the results.

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 0% and the single parameter "kind" is never mentioned in the description. The enum values (campaigns, compare) hint at scope, but an agent gets no explanation of what a kind is, whether it is optional in practice, or what happens when it is omitted.

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 a specific verb+resource ("List saved dashboard filters") and even cites the underlying endpoint (GET /v1/saved-views), which lets an agent distinguish it from savedViews_create and savedViews_delete. It stops short of differentiating the near-synonym naming ("saved views" vs "saved dashboard filters"), but the intent is unambiguous.

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?

There is no when-to-use guidance at all: nothing says whether this is the canonical way to retrieve saved views for re-use, nor whether the kind filter is needed before calling related tools. The description also doesn't mention the sibling write operations (savedViews_create, savedViews_delete) or when to prefer them.

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