colab_session_get

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses error conditions (SESSION_NOT_FOUND, AUTH_EXPIRED, CLI_ERROR) and returned fields, and 'Get status' implies a read-only operation, but it does not explicitly describe permissions, auth handling, or side effects.

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 front-loaded with the core purpose and uses a clean Args/Returns/Raises structure. It is reasonably concise, though the Returns section partially duplicates information already available via the output schema.

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 simple getter with one parameter and an output schema, the description covers the parameter meaning and important error cases. It lacks guidance on alternatives and session-name semantics, which are needed for reliable tool selection.

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?

Schema description coverage is 0%, so the description must compensate. It clarifies that 'name' means the session display name, which is useful, but it does not explain format, constraints, or how display name relates to session_id.

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 states a clear verb and resource: get status of a specific Colab session. It is distinguishable from sibling tools like colab_session_list because it targets one named session, but it does not explicitly name sibling alternatives or contrast use cases.

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 by 'specific Colab session': use this when you already have a session name and need its status. However, the description does not state when to prefer this over colab_session_list, colab_session_get_url, or colab_session_log, nor does it mention prerequisites.

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