workload_overview

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read. The description adds the scope of data returned (workloads plus recent and currently-running runs), which is modest but real context beyond the annotation; it does not cover pagination, limits, or freshness of the data.

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 short clause with no padding, and the core content (workloads, runs, running one) is front-loaded. It is efficient, though the trailing 'Workload view' phrase adds little.

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?

With no parameters, no output schema, and a readOnly annotation, the description carries a light burden and mostly meets it by stating the returned content. However, for a tool sitting among many overlapping workload_* siblings, it lacks the routing and scope detail needed to be confidently selected.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies per the scoring rules.

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 says what is returned (workloads, recent runs, the running one) but is phrased as a noun fragment rather than a clear verb+resource operation, and it names no sibling to differentiate from workload_list or workload_run in the dense workload_* family. An agent can guess it's an overview/read tool but cannot cleanly tell it apart from its neighbors.

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 only usage cue is 'for the Workload view', which is an app-surface reference rather than a when-to-use rule. No alternatives, prerequisites, or exclusion conditions are given, so the agent has no guidance on when to pick this over workload_list or workload_run.

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