Get Current Update Set

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

The annotations already declare readOnlyHint: true, so the agent knows this is a safe read operation. The description adds the 'for the session' scoping detail, which is useful context beyond the annotations. However, it does not disclose what happens if no active update set exists, potential errors, or the exact return format, leaving some behavioral gaps.

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 containing exactly the necessary information—no wasted words. It is concise and well-structured, making it easy for an agent to parse quickly.

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's low complexity (one optional parameter, no output schema, read-only annotation), the description is mostly complete. It clearly states what is retrieved. However, it omits any detail about the return object's shape or possible error conditions, which would be useful for full completeness, especially since no output schema is provided.

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 schema description coverage is 100% for the single 'instance' parameter, so the schema already fully documents its purpose. The description adds no parameter-related information, which is acceptable given the schema's completeness. The baseline score of 3 applies because the structured data does the heavy lifting.

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 a specific verb ('Get') and resource ('currently active update set'), which distinguishes it from sibling tools like 'list_update_sets' (lists all) and 'set_current_update_set' (sets). The phrase 'for the session' adds scope, making the purpose unambiguous.

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 indicates when to use the tool—when you need the active update set in the current session. However, it does not explicitly mention alternatives or exclusion criteria, such as 'use list_update_sets to see all sets' or 'use set_current_update_set to change it.' Despite this, the context is clear enough for an agent to infer appropriate usage.

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