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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value on top: it discloses that each row carries a direction discriminator and that payment-processor identifiers are deliberately withheld, which is behavior an agent cannot learn from the schema.

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 dense sentence front-loads the payload (status and amounts), then qualifies scope (both directions) and the direction values. There is no filler or restatement of the title.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so partially — status, amounts, and the direction field are named, plus a privacy boundary. It omits ordering, pagination/volume, and amount formatting (currency), which are minor but real gaps for a no-output-schema tool.

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, which is the baseline-4 case. There are no argument names for the description to explain, and it correctly spends no words on nonexistent inputs.

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 resource (the member's invoices) and scope (both sent and received), making it easy to separate from siblings like my_bookings or my_profile. It is clear and specific, but never explicitly contrasts with submit_my_invoice, the write-side sibling an agent might confuse it with.

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?

Usage is implied by the name and the zero-parameter signature — there is only one sensible thing to do with this tool — but the description provides no explicit when-to-use or when-not, and does not name submit_my_invoice as the alternative for creating rather than viewing invoices.

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