skypilot_jobs_dashboard

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that it opens the default web browser and provides a dedicated monitoring view, which is useful behavioral context beyond the annotation. However, with an output schema present and no mutation concerns, the remaining behavioral disclosure is limited.

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?

Two concise sentences, front-loaded with the primary action and then a clarifying note about the view. There is no redundant or wasteful language.

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 no parameters, an output schema, and readOnly annotation, the description is largely complete. It could mention whether authentication or a running dashboard server is required, but for a simple browser-opening tool, it provides adequate context.

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 accepts zero parameters, so there is no parameter semantics to document. Per the guidelines, zero parameters gives a baseline of 4. The description appropriately focuses on the action rather than parameters.

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 specific action and resource: opening the managed jobs dashboard in the default browser. It clearly distinguishes from siblings like skypilot_dashboard (general dashboard) and skypilot_managed_job_queue (querying queue data) by specifying 'managed jobs dashboard'. It lacks mention of sibling alternatives, but the resource is 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?

Usage is implied: use this to visually monitor managed jobs. There is no explicit when-to-use guidance or reference to alternatives such as skypilot_dashboard or skypilot_managed_job_queue. An agent can infer the context but must guess at boundaries.

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