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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the return type ('risk scores') but does not mention whether this is read-only, whether it performs computation, what inputs drive the risk tier, or whether results vary by workflow state. The phrase 'residual risk scores' implies aggregation, but that behavior is not explicit.

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 no redundancy. It front-loads the core action and avoids filler. However, it is so brief that it sacrifices useful behavior detail, making it concise but under-informative.

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?

The tool has 4 optional-looking parameters, no output schema details in the description, no annotations, and no usage context. The description is too shallow for an agent to reliably select and invoke this tool among many risk-related siblings. Even with a provided output schema, the input semantics gap makes the description incomplete.

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 undocumented parameters. It does not. The parameters 'decision', 'risk_tier', 'workflow_id', and 'minimum_residual_score' are left entirely unexplained; the description gives no hint about how they relate to the returned risk scores or which are required for a meaningful call.

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 'Return capability-based residual risk scores for agentic workflows' names a specific verb ('Return'), resource ('capability-based residual risk scores'), and scope ('agentic workflows'). It is reasonably clear about what the tool does, though it does not distinguish itself from similar risk-related sibling tools by name.

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 indication of when to use this tool versus the many sibling tools with risk-related names, such as recipes_agentic_aivss_risk_scoring_pack or recipes_agentic_catastrophic_risk_annex. There is no context about the scenario, prerequisite data, or alternatives.

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