trove_search

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

No annotations are provided, so the description carries the full burden. It explicitly states that for secrets, only metadata (title/tags/category) is searched, never values. This is a key behavioral disclosure. However, it could mention case sensitivity, partial match behavior, or result format.

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 sentences, front-loading the action ('Search the vault') and then providing the most important behavioral rules. There is no wasted text, and every sentence adds value.

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?

Given three parameters (all described), no output schema, and no annotations, the description explains the core search behavior and differences between snippets and secrets. It could be improved by mentioning the return format or pagination, but it is largely complete for an agent to understand how to invoke the tool correctly.

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 input schema has 100% coverage with descriptions for each parameter. The description adds meaning by explaining how 'query' behaves differently for snippets (full-text) vs secrets (metadata-only), and summarizes the purpose of 'tags' and 'kind' filtering. This goes beyond the schema descriptions.

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 it searches the vault, specifies different behaviors for snippets (full-text) and secrets (metadata-only), and allows filtering by tags and kind. This distinguishes it from siblings like 'trove_list' or 'trove_get_secret' which have different purposes.

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 when to use this tool (searching, filtering) and provides context that it searches differently based on kind. It doesn't explicitly state when not to use it or name alternatives, but the context is sufficient for typical use cases.

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