get_workflow_improvement_status

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Read' clearly signals a non-mutating operation, and the description adds useful scope by naming the local state and the specific fields returned. It does not cover error cases or the role of output_dir, but for a simple status read this is acceptable.

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 description is a single front-loaded sentence with no filler. Every word earns its place: 'Read' states the action, 'local' sets scope, and the enumerated fields tell the agent what state is exposed.

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 with an output schema, the description mostly suffices: it states local scope and the return categories. However, it leaves the output_dir parameter unexplained and does not guide the agent toward or away from the server-level sibling, creating meaningful gaps.

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 schema has one optional output_dir parameter with no description (0% schema description coverage), and the tool description never mentions it. The description adds no meaning to the parameter, so an agent cannot determine what output_dir affects or how it should be populated.

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 uses a specific verb ('Read'), identifies the resource ('local workflow-improvement' state), and enumerates the exact data categories returned: score, trend, queue, and safety state. The word 'local' also meaningfully distinguishes it from the sibling get_server_workflow_improvement_status.

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 description makes clear this reads local workflow-improvement state, but it never states when to use this tool versus its server-level sibling or other workflow-improvement tools. There is no explicit alternative, exclusion, or when-not-to-use guidance; usage must be inferred from the word 'local'.

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