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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuine context beyond that: the search is lexical rather than semantic, it operates on a pinned public snapshot, and hits are unapproved matches rather than vetted proposals.

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 short, front-loaded sentences with no filler; the core action comes first and the caveat about result semantics follows. Nothing is redundant with the title or schema.

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 four-parameter search tool with no output schema and no schema descriptions, the description should clarify parameter meaning and how it differs from read_knowledge. It does address result semantics, which is valuable, but leaves the parameter surface entirely unexplained.

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% across four parameters (query, limit, domain, project), so the description carries the full documentation burden and supplies none of it. It never explains what 'domain' or 'project' scope to, what 'limit' defaults to, or the expected query format.

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 ('lexically search') and resource ('pinned public knowledge snapshot'), which clearly distinguishes it from a semantic or proposal search. It does not, however, say how it relates to the sibling read_knowledge, so the differentiation is incomplete.

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?

There is no explicit when-to-use guidance or comparison with alternatives such as read_knowledge or project_updates. The closing clause ('Results are search matches, not approved proposals') hints at a usage caution, but it does not tell the agent when this tool is the right pick.

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