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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'semantic search,' which implies a read-only operation but does not disclose ranking behavior, document source, error conditions, or whether it mutates anything. This is a significant transparency gap for a tool with no annotation safety hints.

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?

The description is a single short sentence with no filler, and the core action is front-loaded. However, it is arguably too terse to support a three-parameter tool with no parameter documentation, so it earns a 4 rather than a 5.

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 tool with three parameters, no output schema, and no annotations, the description is far too thin. It does not explain what topK controls, what namespace refers to, what the search returns, or any behavioral expectations. An agent would have to guess at critical invocation details.

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%, and the description adds no meaning for topK or namespace. The word 'semantic' clarifies that query is a natural-language-style search, but the other two parameters remain completely unexplained. The description must compensate for the empty schema and largely fails to do so.

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 description names a specific verb ('Semantic search') and resource ('indexed documents'), making the tool's function clear. It is reasonably distinguishable from sibling tools like files_list and kvp_get, none of which suggest semantic retrieval. It falls short of a 5 only because it does not explicitly differentiate itself from a potential alternative.

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?

The description implies the tool is for semantic retrieval over indexed documents, but it provides no explicit guidance on when to use it versus alternatives, nor does it state exclusions or prerequisites. There is no mention of what kind of index is expected or when another tool would be more appropriate.

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