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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond annotations: the ordering ('newest first'), the included fields ('terms and status'), and the API-key requirement. It still omits pagination or result limits, which are relevant for an inbox-style listing.

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 two tightly written sentences with no filler. The core content and ordering are front-loaded, and the API-key requirement is appended as a clear prerequisite.

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 annotations covering safety and no output schema, the description is largely complete: it states what is returned, the ordering, and the auth requirement. It would be stronger with a note about pagination or result-size limits, but no critical information is missing for correct invocation.

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 are no parameter semantics for the description to clarify. Per the baseline for zero-parameter tools, a 4 is appropriate.

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 identifies the resource (handshakes sent to and from the organization) and scope (inbox view, newest first, with terms and status). It clearly separates this from action-oriented siblings like ledger_handshake_offer or ledger_handshake_accept, but does not explicitly name alternatives or use a direct verb such as 'list'.

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 provides a prerequisite ('Requires your organization API key') but no explicit guidance on when to use this inbox versus sibling tools such as ledger_handshake_verify or ledger_handshake_accept. Usage is only implied by the inbox framing.

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