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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It implies a read operation through 'Return' but does not state filtering behavior, interaction of the three optional parameters, or whether the tool has side effects. This is thin for a tool with no annotation support.

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 concise sentence with the action and primary output categories front-loaded. There is no filler, though 'and workflow namespace coverage' is slightly awkward and could be clearer.

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 presence of an output schema reduces the burden for describing return values, but the description still lacks parameter semantics, usage context, and behavioral details. For a tool with three optional filters and no annotations, an agent cannot confidently determine correct invocation behavior.

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 schema has 0% parameter description coverage and the tool description does not explain namespace, workflow_id, or connector_id. Their names give hints, but the description does not clarify whether they are independent filters, how they combine, or what an all-null call returns.

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 clear verb, 'Return', and identifies a specific resource: MCP connector trust, with named output categories (tiers, controls, evidence, workflow namespace coverage). However, 'workflow namespace coverage' is ambiguous, and it does not distinguish this tool from many sibling recipes_* trust/risk/intake packs.

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 guidance about when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or how to choose between this and similar tools like recipes_mcp_connector_intake_pack or recipes_mcp_risk_coverage_pack.

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