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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds two genuinely new facts: results are limited to PUBLIC conversations, and search terms are not logged — the latter being a privacy disclosure an agent may need when handling sensitive queries. Pagination and result caps are still unstated.

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 compact clauses, zero filler, with the core action front-loaded before the privacy note. It is telegraphic to the point of dropping articles, which slightly hurts readability but wastes nothing.

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 search with rich annotations, the description is mostly sufficient: scope, matching mode, and a privacy note. But with no output schema and no mention of visit_id, result limits, or ordering, an agent cannot fully predict what it gets back or what visit_id does.

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 must carry parameter meaning. It covers q ('literal text') and topic ('optional topic') loosely, but visit_id — a 32-hex-character constrained string — is never mentioned in the description or the schema, leaving a required-looking mystery parameter undocumented.

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 (Search) and a specific resource scope (public signed conversations) with a matching mode (literal text, optional topic). An agent can distinguish it from read_threads/read_thread as a search rather than a list/read. 'Signed conversations' is domain jargon that isn't unpacked, which keeps it from a 5.

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 statement of when to use this versus read_threads or read_thread, and no prerequisites. 'By literal text' hints that matching is exact-substring rather than fuzzy, but the agent must infer that and gets no guidance on narrowing by topic first.

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