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, and it discloses almost nothing beyond the return vocabulary. It does not state whether the operation is read-only or generative, whether a missing workflow_id yields all workflows or an error, whether minimum_score filters results, or what the scorecard actually contains.

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 filler or redundancy. It is efficient, though its brevity is closer to under-specification than to disciplined concision.

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 needn't be described, but that is the only thing excused. With zero annotation coverage, 0% parameter documentation, and no workflow/prerequisite context, the definition leaves an agent unable to invoke this 3-parameter tool confidently.

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% for three parameters. The words "scale, pilot, gate, or block" loosely map to the `decision` filter and "minimum_score" is plausibly the threshold referenced by those labels, but `workflow_id` is never explained and no type/format/allowed values are given. The description adds only marginal meaning over the bare schema.

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?

"Return generated scale, pilot, gate, or block decisions for agentic workflows" names a verb (return), a resource (decisions/scorecard), and enumerates the decision values. However, it never clarifies whether the tool computes these decisions or merely retrieves stored ones, and against ~70 sibling "recipes_*" packs (posture_snapshot, quality_report, assurance_pack) an agent cannot tell when this one applies.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The description gives a bare capability statement with no indication of the precondition for calling it (e.g., does a workflow_id need to exist first, is this the entry point or a follow-up read?).

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