search

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

With readOnlyHint:true annotation, the safety profile is known. The description adds that the tool supports full-text and frontmatter-based structured search, which is a relevant behavioral detail. However, it does not disclose result format, pagination, or other behavioral traits, so it barely exceeds the annotation baseline.

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 two short sentences, starts with the action verb 'Search', and contains no redundant information. It is highly efficient.

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?

While the schema is rich and the annotation covers read-only safety, the description omits any mention of the output/result structure or practical guidance on choosing between text and structured modes. With no output schema, the agent is left to infer what a search result looks like, making the description incomplete for full autonomous use.

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?

The schema already provides complete descriptions for all five parameters, including query syntax with an example for structured filters. The description adds no new parameter-level info beyond reinforcing that both text and structured search modes exist, matching the mode enum.

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 clearly states the tool performs searches across the AI vault, with explicit mention of both full-text and structured (frontmatter) search modes. This distinguishes it from sibling tools like read or project_context, even though it doesn't name them.

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 provides no guidance on when to use search versus alternatives such as read or project_context, and no exclusions or conditions are mentioned. The only usage context is the availability of two search modes, which is more a feature than a usage guideline.

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