snowflake_get_current_context

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

With no annotations, the description carries the full burden. It clearly indicates a read operation ('Retrieve') and lists the returned context fields. It does not disclose edge cases like missing sessions or errors, but for a zero-parameter read, this is largely sufficient. Slight deduction for not explicitly stating read-only behavior or prerequisites.

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, front-loaded sentence that states the action and the specific context items. Every word adds value, with no repetition or filler. It is appropriately sized for a zero-parameter tool.

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 presence of an output schema, the description does not need to explain return formats. For a zero-parameter read that lists the exact fields it retrieves, the description is fully complete. Nothing an agent needs to know to invoke it correctly 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?

The tool has zero parameters, so the baseline per the rubric is 4. The description does not need to explain parameters, and the schema already confirms an empty properties object. No additional parameter semantics are required.

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 'Retrieve' with a clear resource 'current active session context' and enumerates the exact fields (user, role, warehouse, database, schema, account). This unambiguously distinguishes it from the many sibling tools, which target other Snowflake objects.

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 clearly implies when to use it (when session context is needed) but does not explicitly state alternatives or exclusions. It is a unique retrieval tool among siblings, so the context is understandable, yet no explicit guidance about when not to use it is given.

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