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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: newest-first ordering, the payload shape (product + any existing answer), and an auth requirement ('Needs the user's Cotlet API key with access to this app').

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 first and second sentences are near-verbatim duplicates ('newest first, each with its product and any answer'), so the definition repeats itself rather than front-loading new information. Removing the redundant sentence would tighten it with no loss.

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, complete annotations, and a documented sibling for the follow-up action, the description covers purpose, ordering, contents, auth, and next step. Only the redundant phrasing and the unexplained question_id reference hold it back.

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 coverage is 100%, so both parameters are already documented. The description adds only a gloss for unanswered_only ('what needs a reply') beyond the schema's 'Skip questions you already answered.' Note it references a 'question_id' to pass onward, but no such parameter exists in this schema, which slightly muddies the parameter picture.

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 (questions from the Q&A section of your store), and specifies sort and contents (newest first, each with its product and any answer). Clearly distinguished from the sibling answer_buyer_question, which it explicitly names.

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?

Gives actionable usage guidance: 'Set unanswered_only to see what needs a reply' and routes to the sibling with 'Pass question_id to answer_buyer_question.' It stops short of explicit when-not-to-use conditions, 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.