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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context: sort order (most recent first), the data source, and an auth requirement (Cotlet API key with app access) that the annotations do not provide.

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?

Front-loaded with the resource and contents, then the needs_reply behavior, then the auth requirement. Efficient, though the first sentence's parenthetical list of fields is slightly dense and the auth note could be placed more prominently.

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 read-only list tool with no output schema, the description covers what is returned (retailer, last message, reply-needed status), ordering (most recent first), the filter, and the auth prerequisite. Nothing essential for correct invocation 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?

Schema description coverage is 100%, so all three parameters (limit, cursor, needs_reply) are already documented in the schema. The description reinforces what needs_reply does but adds no new syntax or constraint details beyond the schema.

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?

States a specific verb (Lists) and resource (conversations with retailers) and clarifies what is included (retailer, last message, reply-needed flag). The description distinguishes this list tool from the sibling faire_get_conversation and faire_reply_to_message by scope.

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?

Explains the needs_reply toggle to filter for threads waiting on the user, and notes the data source (Messages tab). It does not explicitly route to a sibling like faire_get_conversation for single-thread detail, but the context is clear.

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