Query KB metadata

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral context ('stateless, no full content'), which explains why it's a lightweight query. 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?

One concise sentence (20 words) that front-loads the core functionality and constraints. No redundant 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 7 parameters, no required, and no output schema, the description is minimal. It does not cover pagination, error handling, or result structure. While adequate for a simple filter, it leaves gaps for a complex schema.

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 57%, so the description partially compensates by listing filter fields. However, it does not explain parameter combinations, format requirements, or how limit/pagination works. Schema provides descriptions for some params like type and family, so description adds marginal value.

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 filters metadata-only records by specific fields (family, type, tag, keyword, pi_code, id) and explicitly notes it is stateless with no full content. This distinguishes it from siblings like gkb_read_kb_content.

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 implies usage for metadata-only lookups via 'no full content' but does not explicitly state when to use this tool instead of siblings like gkb_micro_query or gkb_read_kb_content. No when-not-to-use guidance is provided.

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