workload_chat_context

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

The readOnlyHint=true annotation covers the safety profile, so that dimension is handled. Beyond it, the description adds only the truncation-to-limit behavior; it does not explain what the workload/run objects must contain, how the context is assembled, or whether the output is mean to be passed to another assistant. For a context-builder tool this is thin.

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 dense sentence that front-loads the output and its contents before the usage hint. No wasted words, though the sentence is over-packed and slightly convoluted.

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?

No output schema exists, so the description should explain the return shape; it does describe contents and the character cap, which is adequate, but the nested-object parameters and the intended downstream consumer remain unexplained. Borderline minimum viable.

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% and all three parameters (workload, run, limit) are documented only by bare type titles. The description names the concepts workload, last run, table definitions, which maps loosely, but gives no format, structure, or default semantics for the nested object 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 it returns context text sent with a Workload chat question, listing contents (workload, last run, table definitions). But 'workload_chat_context' is ambiguous versus siblings like workload_ask or sql_editor_assistant; it's unclear whether this generates context or retrieves an existing context. The purpose reads as vague rather than a crisp verb+resource.

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 trailing phrase 'for asking in the Claude chat instead of the in-app assistant' hints at a use case but gives no explicit when-to-use/when-not guidance or named alternative sibling tool. An agent cannot determine from this when to call workload_chat_context versus workload_ask or sql_editor_ask.

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