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

No annotations are provided, so the description must carry the full behavioral disclosure burden. The verb 'Return' suggests a read-only operation, but the description does not discuss filtering behavior, optionality semantics, or any side effects. It is not misleading, but it is too thin to be transparent given the absence of annotations.

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, front-loaded sentence with no filler and clearly communicates the tool's output categories. It is concise, though the brevity contributes to the lack of usage and parameter guidance.

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 the return shape does not need to be spelled out, and the four optional parameters are listed in the schema. However, with no annotations, no parameter explanations, and no usage guidance, the description is not complete enough for an agent to know how to select or parameterize this 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?

Schema description coverage is 0%, and the description does not explain how status, trust_tier, workflow_id, or dimension_id affect the result. Parameter names give some hint, but the tool description adds no meaning beyond the raw schema and does not compensate for the complete lack of schema descriptions.

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 names a specific verb ('Return') and a specific resource ('Agent Trust Fabric dimensions, workflow tiers, source evidence, and buyer proof'), so an agent can tell this is a retrieval tool focused on trust-fabric data. It does not explicitly differentiate itself from nearby sibling tools like recipes_secure_context_trust_pack or recipes_a2a_agent_card_trust_profile, but the wording is specific enough to convey the core purpose.

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 on when to use this tool versus the many sibling trust/risk/pack tools, nor any mention of what scenarios favor this pack. The description implies a read/query use case but provides no context about prerequisites, alternatives, or exclusions.

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