colab_get_cpu

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

No annotations are present, so the description must carry behavioral weight. 'Get' implies a read-only operation, but nothing is said about side-effect safety, behavior when session_id is omitted, or whether an error is raised for invalid sessions. The description only names the metric without disclosing operational behavior.

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?

A single front-loaded sentence with no filler; every word contributes to naming the operation and resource. It is efficient, though the brevity leaves behavioral details to other dimensions.

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 one-parameter read tool, the core action is clear, but with no annotations and no output schema the description still leaves gaps: there is no statement of the return shape, default behavior, or invalid-session handling. It is minimally adequate but not complete.

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 gives only a parameter name with no description (0% coverage), so the description needed to explain session_id. It does not; 'for a runtime session' is only a loose mapping and does not state whether the parameter is optional, what format it should be in, or what happens when it is absent.

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?

States a specific read operation ('Get') on a well-defined resource ('CPU core count and utilization') scoped to 'a runtime session'. The resource name differentiates it from sibling metrics tools like colab_get_gpu and colab_get_memory, so an agent can select it unambiguously.

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 'for a runtime session' gives some context for when to call it, but the description does not mention alternatives, exclusions, or prerequisites such as needing an active session. Usage is implied rather than explicit, so this is not strong routing guidance.

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