search_workspace

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

No annotations exist, so the description carries full burden. It mentions 'autocomplete' and 'lightweight fallback', implying limited results, but does not detail behavior like case sensitivity, fuzzy matching, or result limits. The output schema likely covers return format, so details are partially provided. Slight gap in behavioral specifics.

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 sentences, no fluff. The purpose is stated first, followed by the usage guideline. Efficient and well-structured.

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 an output schema available and only 2 parameters, the description is largely complete. It differentiates from similar tools and provides usage context. Minor omission: no mention of pagination or result limits, but acceptable for a lightweight autocomplete 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 covers both parameters with descriptions (100% coverage). The description adds no parameter-specific details beyond the schema, only context about what is searched. Baseline 3 is appropriate as the schema already provides meaning.

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 searches for tasks, resources, and configuration using autocomplete. It differentiates from the sibling workspace_chat, which uses semantic search for richer results. The verb 'search' and resource 'workspace' are specific.

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?

Explicitly states when to use this tool (lightweight autocomplete fallback) and when not to (prefer workspace_chat for most queries). Provides a clear alternative and context, meeting the highest standard.

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