query_knowledge_base

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

Describes semantic search ranking by relevance and recency, and lists sources. With no annotations, it provides basic behavioral context but omits error handling, rate limits, or access restrictions beyond the API key.

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 plus a brief note on credits and API key is efficient. Purpose is front-loaded, though parameter documentation is missing.

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 noted but no details, and five parameters, the description is adequate for a search tool but lacks parameter explanations and error/edge-case context.

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 0%, and the description provides no parameter-level guidance. Parameters like category and document_type are left unexplained, forcing reliance on names only.

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 it searches the SEO knowledge base comprising blogs, docs, and Google guidelines, with semantic search. It distinguishes from sibling tools like get_google_guidelines by covering multiple sources, but could be more explicit about its uniqueness.

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?

Mentions credit cost and API key requirement, implying a paid/searched usage context, but lacks explicit guidance on when to use versus sibling tools like get_google_guidelines or when not to use it.

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