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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful context: the FTS5 engine (implying query syntax and ranking behavior) and the corpus scale (36,628 chunks, 106,308 triples). It does not disclose result ordering, pagination, or whether both corpora are searched or merged in one call.

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 front-loaded sentence with zero filler that surfaces the search engine and corpus targets immediately. The exact record counts are borderline noise, but they do convey scale, so little needs trimming.

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 two-parameter search tool with annotations present and no output schema, the definition covers what is searched but not how results are returned (fields, ranking, snippets, pagination via limit). An agent can invoke it, but cannot predict the response shape or how the two corpora are combined in results.

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 100%, so both parameters are already documented, making 3 the baseline. The description adds the FTS5 detail, which hints that the query accepts full-text syntax, but it gives no syntax examples or clarifications, and notably does not resolve the tension that the schema describes query as being for the 'creator knowledge graph' alone.

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 mechanism (FTS5 search) and the exact corpora it queries (video transcript chunks, knowledge graph triples in vault.db), so an agent knows precisely what it retrieves. Sibling tools (gcp_catalog_search, package_health_pulse, security_cve_audit) occupy entirely different domains, so implicit differentiation is sufficient, though no sibling is named explicitly.

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 statement of when to use this tool, when not to, or what alternative to pick. The corpus inventory implies it is for vault knowledge lookups, but no conditions, prerequisites, or exclusions are given, so an agent must infer selection criteria.

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