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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely new behavior: results are ranked, include a snippet, put drafts last, and exclude archived pages entirely. It also discloses the cost ('Free'), which matters alongside the billing sibling, but says nothing about result volume beyond the schema's limit or about rate limits.

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 core action in the first sentence, then query syntax, then result ordering/filtering, then the persona-filter use case. Very dense with no filler, though the trailing 'Free.' fragment and the run-on persona sentence make it slightly less scannable than it could be.

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?

Two parameters, no output schema, and the description covers the action, query grammar, return shape (ranked pages with snippet), ordering, exclusion of archived items, and billing. The only real gap is what a returned 'page' contains beyond a snippet and how to then read it, which the sibling read tool presumably handles.

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 50% — only `limit` is documented in the schema, so `q` relies on the description, which fully compensates by specifying query syntax (quoted phrases, `or`, -exclusions). `limit` is already covered by the schema's range and default, so the description does not need to repeat it.

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 concrete verb and resource: search this workspace's second brain, returning ranked pages with snippets. It implicitly separates itself from hyreflow_knowledge_read/write/index by being the retrieval-by-query tool, but it never names those siblings explicitly, so the distinction is inferred rather than declared.

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 clear operating context: web-search style query with quoted phrases, `or` and -exclusions, and points to Persona Search filter pages as the right target when building a people search with the provider tools. It stops short of stating when to prefer hyreflow_knowledge_read (fetching a known page) over searching.

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