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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the bar is lower. The description adds genuine value beyond them: results are private to the connected account, each view is a snapshot for comparison rather than a compliance verdict, and write/delete operations live outside this tool.

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?

Three tight sentences with no filler: scope first, then the interpretation caveat, then the access limitation. Nothing is repeated from the name or annotations, and the most important constraint is front-loaded.

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 an output schema present, the description need not explain return fields, and it supplies the scope and caveat an agent needs to interpret them. It is essentially complete for a zero-parameter list tool; only the relation to get_saved_role_view is left implicit.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly introduces no parameter-like concepts.

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 gives a specific verb and resource ('List private role and country research views') plus ownership scope ('belonging to the connected account'), so an agent knows exactly what comes back. It does not name the singular sibling get_saved_role_view or explain how the two differ, so it falls short of full sibling differentiation.

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?

It states the read-only nature and clarifies that saving and deleting views require the person's own HTTP account access, which effectively tells the agent this tool cannot mutate anything. No explicit alternative (e.g. get_saved_role_view for a single view) is named, so the routing guidance is implied rather than complete.

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