Select favourite view

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

Adds substantial context beyond annotations: describes the side effect on rillsoft_view_state_get ('reports favorite next to the underlying view name'), clarifies it only changes display (not project data), and notes it is not an undo step. Annotations say readOnlyHint=false but the description clarifies this is a view-only, non-destructive switch, consistent with destructiveHint=false.

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?

Two tight sentences front-loading the action, followed by behavioral notes and sibling routing. Every clause earns its place.

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 1-param switch tool with an output schema present, the description covers the visible effect, the state report, non-undoability, and sibling alternatives. Nothing an agent needs is missing.

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 coverage is 100% and the single parameter 'name' is fully described in the schema as 'name of the favourite view from rillsoft_view_favorite_list'. The description mentions 'name' but adds no syntax or format guidance beyond the schema baseline.

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?

States a specific verb 'Switches' and resource 'the visible view to the favourite view name', and explicitly distinguishes from sibling operations for creating/deleting favourites.

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?

Clear context: use to switch to a favourite, and names the create/delete siblings for other operations. However it does not state when to prefer rillsoft_view_state_apply or rillsoft_view_columns_apply over this tool, though those are adjacent concerns.

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