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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is fully covered structurally. The description adds nothing beyond a pointer to describe_operation — no pagination, ordering, or shape of what is returned.

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?

It is short, but the first two sentences are verbatim duplicates and carry no information, so they do not earn their place. The one useful clause (describe_operation) is buried at the end.

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?

No output schema and no parameter documentation mean the description must carry the burden for a nested-object, free-form-query tool, and it does not. An agent still needs a second call to describe_operation before it can construct a valid request.

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 both parameters (a free-form `query` object and an empty `params` object) are undocumented. The description offers no meaning for either; its only mitigation is deferring to describe_operation, which is a routing hint rather than parameter semantics.

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 only restates the title and HTTP path ("GET /api/saved-views") twice, which is a tautology of the name/title. It does imply a read of the saved-views collection, but gives no scope, filtering, or differentiation from the sibling get_saved_views_by_id.

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 only actionable guidance is that "describe_operation provides native request schemas," which hints at a discovery workflow but not when to call this tool versus get_saved_views_by_id or other list endpoints. No conditions, prerequisites, or exclusions are stated.

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