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

The 'Read-only' sentence merely restates readOnlyHint and earns no credit. What does add value is 'Returns titles, URLs and excerpts', since no output schema exists and this is the only disclosure of result shape. It still omits ranking/relevance behavior, whether excerpts are truncated, and any rate or corpus-version caveats.

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?

Three short, front-loaded sentences with the corpus scope first and return shape second. The trailing 'Read-only' is redundant with the annotations and is the one sentence that does not earn its place.

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 simple three-parameter search tool with no output schema, the description covers what it searches, what comes back, and that it is safe. The remaining gap is query formulation guidance, which matters more here than for a highly structured tool.

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 67% and both optional parameters (lang, top_k) already document their defaults and ranges in the schema; the undescribed 'query' parameter is self-evident. The description adds nothing about query semantics, e.g. whether it accepts natural language or keyword syntax, so the baseline 3 applies.

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 the Vericto documentation') and pins the scope by identifying the corpus ('the same corpus as the site assistant'), which no sibling tool touches. An agent can tell immediately that this is the documentation lookup tool rather than a config or rule tool.

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?

Usage is implied by the name and the 'same corpus as the site assistant' framing, so an agent can infer this is for answering docs questions. However, there is no explicit when-to-use or when-not guidance and no mention of alternatives (e.g., when to prefer open_support_ticket or check_sql instead).

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