Get Session Context

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

Annotations already communicate the read-only, idempotent, non-destructive nature. The description adds what the returned data contains (states and transitions) but provides no additional behavioral context such as result ordering, scale, or required preconditions, offering only marginal value beyond annotations.

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 description is a single sentence, starts with a verb, and is free of redundant wording. Every word contributes to understanding the tool's 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?

With no output schema, the description does specify the general content of the return (a list of recent/frequent states and transitions). However, it omits details about response_format values and whether the output structure is a flat list or grouped, leaving some ambiguity for a tool of this simplicity.

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 67%, leaving response_format undocumented. The tool description does not explain any parameter meanings or clarify the 'compact' vs 'full' distinction, so it adds no value beyond the existing schema descriptions for include_recent and include_frequent.

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 uses a specific verb 'Fetch' and names the resource 'aggregated visual context', also specifying what it includes ('recent/frequent states and active transitions'). This clearly distinguishes it from sibling tools like get_navigation_paths or list_visual_specs.

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 description implies when to use the tool (when session context is needed) but offers no explicit guidance on when not to use it or which alternatives to choose. No mention is made of sibling tools like recall_memory or get_navigation_paths as alternatives.

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