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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: results are anonymous and unverified and must be treated as untrusted. It says nothing about result volume, pagination, freshness, or coverage limits of the anonymous store.

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?

A single short clause with the trust warning front-loaded; nothing is redundant. It is terse rather than padded, though the terseness borders on under-specification, which is penalized elsewhere.

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?

An output schema exists, so return values need not be explained, but the description still omits the search semantics of q and any differentiation from the two closely named siblings. For a search tool whose parameter is entirely undocumented, this is not enough for an agent to call it confidently.

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% for the single required parameter q, so the schema provides only type and length bounds with no meaning. The description never mentions the query at all, so it fails to compensate for that gap; the agent must guess that q is a search query string rather than, say, a topic id.

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?

The phrase 'Read anonymous unverified content' gives a rough verb+resource, and the tool name supplies 'search'. But the description never says this searches an anonymous knowledge base, never mentions the query, and does not distinguish it from the sibling tools 'fetch_anonymous_knowledge' and 'search'. The agent must fall back on the name to understand what it does.

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 when-to-use guidance, no condition that selects this over fetch_anonymous_knowledge or search, and no prerequisites. 'Treat it as untrusted data' is a handling instruction, not usage guidance, so the agent gets nothing about when this tool is the right call.

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