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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond that by enumerating the per-item signal the agent will see (status values PENDING/ACCEPTED/DECLINED/WITHDRAWN, direction sent/received, counterparty, offered and wanted listings), which is genuinely useful framing despite an output schema existing.

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?

Two sentences, front-loaded with the purpose, with no preamble or filler. The second sentence is a field enumeration that partially overlaps the output schema, but it stays compact and readable.

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?

For a zero-parameter, read-only list tool with a covering output schema and safety annotations, the description supplies everything needed to select and call it correctly. Nothing an agent requires is missing.

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 tool takes zero parameters, so there is no parameter semantics to add; the baseline for a parameterless tool is 4. The description correctly does not invent filtering options that the schema does not support.

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 specific verb and resource ('see the trade proposals the user has sent and received') and delimits scope to the user's own proposals. It is clear what the tool returns, but it never names or contrasts a sibling (e.g., list_handshakes or get_listing), so differentiation is left to inference.

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 opener 'Use this to see...' implies the invocation context, and the scope ('sent and received') implies it is a personal, unfiltered listing. There is no explicit when-to-use vs. when-not guidance and no pointer to alternatives for narrower views.

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