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 word 'Return' implies a read-only operation, but the description does not state whether results are filtered, summarized, or affected by the optional parameters, nor does it describe any side effects, permissions, or output behavior.

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 filler and states its main subject immediately. It is economically written, though the dense compound noun phrase 'MCP tool annotation, trust, and session-combination risk evidence' borders on jargon.

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?

There is no output schema and no annotations, so the description alone must explain the tool's complete contract. It omits parameter semantics, output format, call patterns, and any relationship to the large set of sibling risk/trust/evidence tools, leaving a substantial gap for an agent trying to invoke it 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 input schema provides four nullable string parameters with defaults but no semantic descriptions, and the description never mentions decision, namespace, risk_tier, or workflow_id. Schema coverage is effectively zero, and the description makes no attempt to compensate, leaving valid values and their effect on the returned evidence completely unexplained.

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 uses a specific verb ('Return') and names a resource ('MCP tool annotation, trust, and session-combination risk evidence'), so it is not a tautology. However, the object is vague risk/trust jargon and does not clearly differentiate this tool from the many closely related sibling recipes_* risk and trust tools.

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 guidance is given about when to use this tool versus alternatives such as recipes_mcp_risk_coverage_pack or recipes_mcp_connector_trust_pack. There is no context describing typical scenarios, prerequisites, or exclusions, so the agent must infer applicability from the tool name alone.

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