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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds two genuinely new behavioral facts — recency scoping ('recent') and that content excerpts are never returned — but leaves ordering, the meaning of 'recent', and paging behavior unspecified.

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 tight sentences, front-loaded with the resource and scope, and the output constraint is placed second where it reads as a caveat. Nothing is redundant with the title or annotations.

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?

With an output schema present, the description need not explain return values, and it correctly flags the most surprising output trait (no excerpts). The remaining gap is the absence of any guidance on limit/paging, which matters for a list tool with a default of 8 and a hard cap of 16.

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 description coverage is 0%, so the description must carry parameter meaning, yet it only covers postId (and adds that it must be 'verified', which is useful) and provider. The limit parameter and its 1–16 bounds, plus the constant status parameter, get no explanation, and no meaning is added beyond names for provider.

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 gives a specific verb and resource ('List recent published receipt metadata') plus the scope ('recent'), which is far more informative than the title alone. It implicitly separates itself from content-oriented siblings via 'metadata' and 'excerpts are never returned', though it never names an alternative sibling explicitly.

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 only implied: the reader can infer this is the metadata-only listing tool and that filtering is optional by postId or provider. There is no explicit when-to-use versus list_posts/list_ideas guidance, and no statement of when this tool is the wrong choice.

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