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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description merely restates the purpose and gives no information about what 'measurement probes' contain, whether the operation is read-only or mutating, how results are aggregated or filtered, or what the output structure looks like. Even though an output schema exists, the description itself adds no behavioral context.

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 sentence with minimal waste. It front-loads the core verb+resource immediately. It is appropriately sized for what it conveys, though it sacrifices useful detail for brevity.

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 an output schema present and 6 unrequired filter-like parameters, this looks like a query/list tool, but nothing explains what the probes contain, how filters combine, or which scenarios call for this pack versus sibling packs. For a pack whose name suggests a non-trivial domain concept, the definition leaves too much for the agent to infer.

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%, so the description must compensate for the six parameters (status, class_id, decision, probe_id, workflow_id, minimum_score) that have only type/default information. It does not. The description mentions none of the parameters and doesn't explain what they do, how they interact, or what valid values look like. For a tool with 6 undocumented parameters, this is a significant 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 clear action (return measurement probes) and a specific resource (agentic workflow traceability and readiness). It distinguishes itself reasonably from the many sibling tool packs by focusing on 'measurement probes' specifically. However, 'traceability and readiness' is broad and could overlap with siblings like recipes_agentic_readiness_scorecard or recipes_agentic_assurance_pack, so it doesn't fully differentiate.

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 provides no guidance on when to use this tool versus any of the dozens of related sibling packs (readiness_scorecard, assurance_pack, posture_snapshot, etc.). It doesn't state what criteria would lead an agent to select this over alternatives, nor does it mention any exclusions or prerequisites.

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