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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no statement of what the response contains, behavior on a missing/invalid id, or visibility/permission constraints.

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 one substantive sentence is duplicated verbatim, wasting half the text, and the remaining content (operation ID, pointer to describe_operation) is boilerplate rather than front-loaded purpose.

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 by-id lookup with no output schema and undocumented parameters, the description should at least say what a saved view record contains. Instead it delegates everything to describe_operation, leaving an agent unable to predict the response shape.

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 schema uses a nested 'params.id' object with a 1-2000 char string constraint, which is not self-explanatory. The description only hints at ':id' via the raw route and gives no format, source, or example value for the saved-view identifier.

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 HTTP route 'GET /api/saved-views/:id' twice plus an operation ID, which is essentially a tautology of the tool name/title. It never says what a saved view is or what is returned, and it does not distinguish this from the sibling get_saved_views (list) tool.

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 guidance on when to use this versus get_saved_views or any other lookup. The only actionable pointer is a generic 'describe_operation provides native request schemas' note, which is a fallback rather than a usage rule.

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