search_concepts

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

No annotations exist, so description carries full burden. It fully explains behavior: case-insensitive substring match, return up to 20 results with taxonomy tags, or a 'no concepts' message. No contradictions.

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?

Well-structured with summary first, then parameter details and return description. Approximately 100 words with no fluff, earning each sentence's presence.

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?

Complete given context: explains behavior, parameters, return format, and usage context relative to siblings. Lack of error handling details is acceptable for a 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 has no descriptions (0% coverage), but description provides full semantics: domain is exact name from list_domains, query is substring with examples. Return format is also detailed.

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 finds concepts in a domain by partial name, with a specific verb and resource. It distinguishes itself from siblings by advising use before query_ckg or get_prerequisites when exact labels are unknown.

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?

Provides explicit guidance on when to use (before query_ckg/get_prerequisites when label is unknown) and describes the behavior (case-insensitive substring match). Implicitly suggests alternatives for when label is known.

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