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

No annotations, so the description carries the full burden — and it discloses a genuinely important environment-specific trap: the COL shell has search disabled and returns an empty items array, with a recommended workaround. It stops short of describing pagination, result limits, or ranking behavior, which leaves some operational gaps for a search tool.

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-loads purpose, then trigger, then example, then the COL caveat — a sensible information hierarchy. The example call is somewhat redundant with the schema's examples, but nothing is padded or confusing.

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 no output schema, the description does state the return shape (matching pages, posts, and resources) and warns that COL returns an empty items array, which is the critical thing an agent needs. Pagination and result-count behavior remain unaddressed.

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% and both parameters carry detailed descriptions with pattern/maxLength and examples, so the schema does the heavy lifting. The description's inline example call largely duplicates the schema's own examples rather than adding new parameter meaning.

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 and resource ('Full-text search against Siigo's curated content for a country') plus the returned entity types (pages, posts, resources). It also implicitly distinguishes itself from the more specific siblings by framing itself as the fallback topic search.

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 an explicit trigger ('when the user mentions a topic you don't have a more specific tool for') and names concrete alternatives (get_articles, get_compliance_info) for the COL case. Both when-to-use and when-not-to-use are covered.

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