query_domain_knowledge

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

With no annotations, the description discloses it searches and returns Q&A pairs, implying read-only behavior. No mention of side effects, authentication, or rate limits, but it is transparent about its core function.

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 well-structured with a clear purpose, content list, and return format. It is concise but includes useful detail without unnecessary repetition.

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 the presence of an output schema, the description adequately explains the return (Q&A pairs). For a simple search tool, it covers enough context for an AI agent.

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 description explains the top_k parameter (default 5, max 10). The question parameter is implied by the tool's purpose but not detailed. Schema coverage is 0%, so description partially compensates.

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 expert interview transcripts for scientific guidance, specifying the resource and action. It distinguishes from sibling tools which deal with parameters, errors, diagnostics, etc.

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 explains the knowledge base content, helping infer when to use (e.g., needing scientific guidance on MOM6 configuration). However, no explicit when-not or comparison to siblings is provided.

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