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

readOnlyHint=true already covers the safety profile, yet the description still adds value by enumerating what each result contains (text, date, outlet, source_url, ready-made attribution) — important since there is no output schema. It stops short of stating result ordering for non-empty queries or whether matching is fuzzy or exact.

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 purpose and followed by result shape. The example list is slightly redundant with the schema's query description, but the cost is small.

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 usefully compensates by listing returned fields and the attribution convenience. For a two-optional-parameter read tool with annotations covering safety, nothing critical is missing beyond result ordering and match behavior.

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 are documented there, so the baseline is 3. The description's query examples are richer than the schema's, but its "empty query returns the latest" clause largely restates what the query parameter description already says, and it adds nothing about limit.

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 ("search his curated quotes") and seeds it with concrete topic examples ("trust", "Shenzhen", "tariffs"), which tells an agent exactly what corpus is being queried. It does not explicitly distinguish itself from the similarly named sibling search_coverage, so the agent must infer the split from names alone.

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?

The line "Empty query returns the latest" gives one concrete usage condition (browse mode vs topic mode). However, there is no guidance on when to use this rather than search_coverage or get_profile, and no exclusions or prerequisites are stated.

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