search_context

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

No annotations provided. Description discloses search scope (frontmatter and body) and return fields but omits details like authentication needs, rate limits, or any side effects beyond read-only nature.

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 concise sentences with purpose immediately stated. No fluff, every sentence adds useful information.

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?

With output schema existing, return values are covered. Description specifies returned fields. Minor gaps like pagination or case sensitivity, but overall sufficient for a simple search 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 0%, so description adds value by explaining 'query' is the search string and 'limit' restricts results. No further format details, but adequate for simple parameters.

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?

Clearly states it searches contexts by query string, covering both frontmatter and body. Differentiates from sibling tools (delete, get, list, put) which are not search-oriented.

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?

Implies usage for searching contexts, but lacks explicit when-to-use or when-not-to-use guidance. However, sibling names help differentiate.

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