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. 'Return' weakly implies a read-only report, but there is no disclosure of permissions, rate limits, side effects, or what scope the returned trust data covers.

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 definition is a single front-loaded sentence with no filler. It is appropriately terse, though its brevity contributes to under-specification rather than being a structural flaw in itself.

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 is present, so return values need not be explained. However, with three undocumented input parameters, no annotations, and no usage guidance, the description is not complete enough for an agent to know how to scope or invoke the tool 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?

All three parameters (namespace, workflow_id, connector_id) have 0% schema description coverage, and the description does not explain what any of them filter or control. The phrase 'workflow namespace coverage' is output-oriented and does not compensate for the missing parameter semantics.

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 verb (Return) and a resource (MCP connector trust tiers, controls, evidence, workflow namespace coverage), but the purpose remains vague because the listed concepts are broad jargon and the tool is not differentiated from similar sibling trust packs such as recipes_mcp_connector_intake_pack or recipes_mcp_risk_coverage_pack.

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 offers no when-to-use guidance, no prerequisites, and no alternatives among the many sibling trust/connector tools. An agent must infer usage entirely from the tool name and one-sentence summary.

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