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, yet it discloses nothing about mutability, permissions, or side effects. The verb 'Return' weakly implies a read operation, but the description never confirms it, nor does it explain how the six filters interact or what happens when none are supplied.

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 well-formed sentence with no waste and no redundancy. But the brevity comes at the cost of under-specification rather than disciplined conciseness, so it earns only a middling score.

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 need not be described, but for a 6-parameter filtering tool with zero annotation and zero schema-description coverage, the definition leaves the agent unable to construct a meaningful call or predict the result set.

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?

Six parameters with 0% schema description coverage and no enum values, and the description adds no parameter meaning whatsoever. Nothing explains what status, class_id, decision, probe_id, workflow_id, or minimum_score filter on or how they combine.

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 ('measurement probes') with a scope qualifier ('agentic workflow traceability and readiness'). However, 'measurement probes' is jargon that is not defined, and the description does nothing to distinguish this tool from near-neighbors like recipes_agentic_readiness_scorecard, recipes_agentic_telemetry_contract, or recipes_agentic_posture_snapshot.

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 guidance, no prerequisites, and no mention of any alternative sibling in a list of ~70 related recipes tools. The agent must guess whether this is the right tool for a probe/measurement need.

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