get_current_context

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

The description fully discloses the tool's behavior: it returns a string with specific format and explains what each possible value means. The annotation readOnlyHint=true is consistent with the read-only nature of the operation. The description adds significant value beyond the annotation by detailing the return values and their implications for element interaction.

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 three sentences with no wasted words. It is front-loaded with the purpose, immediately followed by specific return value details and usage guidance. Every sentence 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?

Given the tool has no parameters, no output schema, and only a readOnlyHint annotation, the description provides complete context: what it does, what it returns, and when to use it. An agent has all necessary information to correctly invoke and interpret the result.

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 has zero parameters, and schema coverage is 100% (trivially). The description does not add parameter-level semantics because there are none. Per the scoring guidelines, baseline is 3 when schema coverage is high. The description's explanation of the output is valuable but falls under behavioral transparency rather than parameter semantics.

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's purpose: 'Get the current active context.' It specifies the two possible return values (NATIVE_APP and WEBVIEW_<id>) and explains their meanings. This distinguishes it from siblings like get_contexts (which likely returns all contexts) and set_context (which changes context).

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 explicitly advises when to use the tool: 'Call this if unsure which context is active before interacting.' This provides clear guidance on its use case. It does not explicitly name alternatives, but the context is clear enough for an agent to decide when to invoke this versus other context-related tools.

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