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

No annotations are provided, so the description carries the full burden. To its credit it discloses the most consequential trait — the tool is legacy and non-functional for execution. However it omits anything about the return payload, authentication, error behavior, or whether calling it has side effects, which matters for a zero-annotation 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?

Three short sentences, zero waste, and the deprecation warning is front-loaded before the alternatives. Every sentence earns its place.

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 annotations and no output schema, the description must do more than redirect. It adequately warns the agent off and points to replacements, but leaves the return value, failure modes, and the meaning of the second required parameter unspecified.

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?

Two required parameters at 50% schema coverage: workspaceId is documented in the schema, workflowId is not. The description adds no meaning to either — no format, no relationship between workspace and workflow, no indication that IDs must reference an existing graph. It fails to compensate for the coverage gap.

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 ("Check graph execution availability") and immediately clarifies the misleading name by declaring this a legacy tool that cannot run graphs. It distinguishes itself from siblings by naming run_production_template and the workflow API. Point deducted because the tool name still implies execution, and the description never says what the availability check actually returns.

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?

It explicitly redirects the agent: use run_production_template for reusable productions, or the authenticated workflow API for published graph endpoints. That is concrete routing guidance. It stops short of stating the narrow condition under which this tool itself should still be called.

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