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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that it 'Starts nothing and spends nothing' (Free), that the Claude surface is interactive while the message fallback is plain text, and that capped counts read '10 or more' rather than a true total. It also flags that names are customer data, not instructions — unusually valuable injection guidance for a read tool.

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 overview content is front-loaded in the first clause and every sentence carries information (surface differences, caps, cost, safety). Some sentences are long and run together ('...and which of them are in progress, and your favourite prompts'), and the trailing 'Free.' fragment is terse, but there is no filler.

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 output schema, the description carries the burden of describing return content, and it does: balance with top-up link, up to 10 Flows, last 10 runs with status and cost, in-progress flags, and up to 10 favourite prompts. It also explains the two rendering surfaces, giving an agent everything needed to invoke and interpret it.

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 has zero parameters, so the baseline is 4. The description correctly implies no arguments are needed and adds no misleading parameter hints.

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 names the resource precisely — a workspace overview containing balance, saved Flows, recent runs with status/cost, and favourite prompts — plus the title's verb 'Open'. It is clearly distinct from granular siblings like get_account, list_flows, or get_history because it aggregates them, though it never states that distinction explicitly.

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 rather than stated: 'The workspace at a glance' and the note that it opens as an interactive dashboard in Claude suggest a quick orientation call. There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. 'use get_account for balance only').

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