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

No annotations are provided, so the description carries the full behavioral burden. It implies a read via 'Return' but discloses nothing about permissions, auth needs, rate limits, or what the returned policy actually contains. For a zero-annotation tool this is a significant gap.

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 front-loaded sentence with no waste, but its brevity comes at the cost of under-specification rather than economy. Appropriate length is not the same as sufficient structure here.

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?

An output schema exists, so return values are partly covered, but for a zero-annotation policy tool the description omits workflow_id semantics and any behavioral or usage context. It leaves an agent without the information needed to invoke the tool correctly.

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 single workflow_id parameter has 0% schema description coverage, and the description never mentions it or its optional/null-default semantics. An agent gets no indication of whether workflow_id scopes the result or what happens when it is omitted.

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?

States a verb (Return) and a resource (workflow control-plane policy), which is enough to know it's a read tool. However, 'control-plane policy' is vague, and the description does nothing to distinguish it from close siblings like recipes_mcp_gateway_policy or recipes_agentic_control_plane_blueprint.

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?

No when-to-use, when-not-to-use, or alternative guidance is provided. The audience list ('agents, reviewers, and MCP gateways') hints at context but does not tell an agent when to pick this tool over its many siblings.

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