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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the "[read]" prefix is largely redundant. The description does add real value by disclosing the return item fields ({summary, text}) in the absence of an output schema, but says nothing about the unresolved identifier case.

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?

One front-loaded sentence that identifies the resource first and the identifier options second — no filler. The terseness borders on under-specification, but the sentence itself is well-formed and each clause carries information.

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?

The return-shape hint compensates for the missing output schema, which is a genuine plus. However, with zero parameter descriptions and both identifiers optional, the definition leaves an agent unable to determine a valid call in the edge cases, so it is only minimally complete for a lookup 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?

Schema description coverage is 0%, so the description carries the burden and only delivers the alternation wording "given by `collection_id` or `collection_uuid`". It does not state precedence when both are supplied, required-ness when neither is, or the format of the UUID, so the ambiguity of two nullable optional params is left unresolved.

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?

Names a specific verb+resource: fetch the FAQ list of a seliee_collection, and even sketches the returned item shape ({summary, text}). The resource name implicitly separates it from the sibling FAQ tools (get_article_faqs, get_page_faqs, get_website_faqs, get_lead_faqs), but no explicit differentiation is offered.

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?

No guidance on when to use this versus get_collection, list_collections, or the other *_faqs tools, nor on the choice between the two identifiers. Since both parameters are optional, the agent gets no hint about which to supply or what happens if neither is passed — exactly the situation guidance should cover.

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