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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotentHint, so safety is covered. The description adds real value beyond them by specifying newest-first ordering, that each item carries its prospect, and that replying is impossible through this connector, which is useful scoping context.

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 compact sentences with the core content ('most recent inbound replies, newest first') front-loaded and the read-only constraint stated without padding. Nothing is wasted.

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 return-field detail is not the description's responsibility, and the ordering plus prospect association are well covered. The only real gap is the unaddressed limit parameter, which keeps this short of fully complete.

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?

There is a single parameter (limit) with 0% schema description coverage and a default of 20, yet the description never mentions it, its meaning, or how many replies are returned. The phrase 'most recent' hints at bounded results but does not compensate for the undocumented parameter.

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 concrete resource (the signed-in user's inbound replies), the ordering ('newest first'), and the joined context ('with the prospect each came from'). This is instantly distinguishable from siblings like list_leads or get_campaign_stats, and an agent knows exactly what data comes back.

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 explicit when-to-use statement, but 'Read-only: this connector cannot reply' implicitly routes the agent to draft_message for outbound handling. No guidance is given on when to prefer this over get_profile or the campaign tools, so usage remains inferable rather than stated.

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