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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the depth-1 limitation and direction scoping, but does not disclose output shape, pagination, limits, or authentication requirements. No contradiction with 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?

A single, well-structured sentence that front-loads the verb and resource, includes the critical depth constraint, and contains no filler. It is appropriately concise for the tool's complexity.

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 is simple and the annotations carry the read-only safety context, making the description minimally viable for invocation. However, there is no output schema, and the description does not mention what a trust edge result contains, whether pagination exists, or how the context parameter behaves.

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 coverage is 50%, with platform and direction described but context and identifier left undocumented. The description adds a little meaning by framing the query as identity-based trust edges and clarifying outgoing/incoming, but it does not explain the context parameter or identifier format, so it only partially compensates.

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 ('List'), a clear resource ('trust edges'), and a precise scope ('outgoing or incoming', 'for an identity at depth 1'). This distinguishes it from mutation siblings like connect_trust_create and connect_trust_revoke, and from the point-check tool connect_trust_check.

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 implies when to use the tool: when you need a depth-1 view of trust edges in either direction. However, it does not explicitly state when not to use it or name alternatives such as connect_trust_check for verifying a single trust relationship.

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