get_contexts

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

Annotations already mark it as readOnlyHint=true. The description adds valuable behavioral detail by specifying the exact return patterns: 'NATIVE_APP' for the UIA tree and 'WEBVIEW_<id>' for webviews, enhancing transparency 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, focused sentence that efficiently communicates the purpose and return format. While slightly more structure (e.g., separate sentence for return details) could help, there is no waste.

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?

Given no parameters, no output schema, and a simple behavior, the description is complete. It covers what the tool does and what it returns. It could mention that this requires an active session (implied by tool context), but that is a minor gap.

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?

There are zero parameters and schema coverage is 100%, so the description does not need to add param info. The baseline for no parameters is 4, and the description appropriately does not invent unnecessary details.

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 clearly states the tool lists all available contexts, defining the verb 'List' and the resource 'contexts'. It distinguishes from sibling tools like get_current_context (single) and set_context (mutation) by specifying it returns all contexts.

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?

Usage is implied: use this to see available contexts before potentially switching with set_context. However, there is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives like get_current_context for the current single context.

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