knowledgelib-mcp

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

Adds valuable performance context beyond annotations ('shares a single catalog parse') explaining the efficiency mechanism. States batch limit constraint. Does not contradict readOnly/idempotent annotations.

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, each high-value: purpose statement, efficiency rationale with sibling comparison, and operational constraint. No filler text.

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?

Strong coverage for a read-only batch tool with complete schema annotations. Minor gap: no output schema exists, and description does not clarify return structure (e.g., results grouping), though this is somewhat implied by 'batch_query' naming.

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 100% description coverage, so baseline applies. Description mentions 'Max 10 queries' reinforcing the constraint but does not add semantic meaning to individual query parameters (q, domain, etc.) beyond what's in schema.

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?

Specific verb 'Search' + resource 'topics' clearly stated. Explicitly distinguishes from sibling 'query_knowledge' by contrasting single-call vs multiple calls.

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 ('More efficient than calling query_knowledge multiple times') and names the alternative tool. Includes operational constraint ('Max 10 queries per batch') guiding usage limits.

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