get_current_context

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

With no annotations provided, the description carries the burden of behavioral disclosure. 'Show' clearly implies a read-only operation, and the listing of what information is included gives the agent a good sense of the tool's return content. It does not explicitly state 'no side effects', but the non-mutating nature is strongly evident from the verb.

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 two short sentences, front-loaded with the primary purpose and immediately followed by actionable guidance. Every word contributes value; there is no fluff or redundancy.

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 zero-parameter context getter with no output schema, the description explains what will be shown and why it matters, making it fully self-sufficient for an agent to select and invoke correctly. The context about confirming the correct site is particularly useful given the large roster of sibling tools.

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 input schema has zero parameters, and the baseline for zero-parameter tools is 4. The description adds no parameter-specific details because none exist, which is appropriate.

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 ('Show') tied to a clear resource ('current connection context') and enumerates its contents (site_id, API URL, session, account info). This makes the tool's purpose unmistakable and distinguishes it from all sibling tools, none of which claim to expose current connection state.

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 phrase 'Call this first to confirm you're working on the right site' provides explicit when-to-use guidance. It does not mention alternatives or exclusions, but for a context-checking tool, the 'first call' directive is sufficient and clear enough to guide an agent.

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