search_pdf_context_tool

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

No annotations exist, so the description carries the full burden. It transparently describes the tool's behavior (semantic search, page citations, filter usage). However, it does not explicitly state read-only nature or potential limitations like rate limits.

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 concise, with 5 sentences front-loaded with the purpose. No redundancy. Could be slightly more streamlined, but overall efficient.

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 high parameter count (9) and no annotations, the description lacks details on several parameters (top_k, structure_node_id, doc_type). It also does not describe the output format beyond 'page citations'. Incomplete for a complex 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 description coverage is 0%. The description only briefly mentions 'chapter_id/section_id/page filters' but does not detail parameters like top_k, structure_node_id, doc_type, or how to use them. Missing parameter guidance reduces usefulness.

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 'Semantic search over PDFs indexed by this MCP server only', specifying the verb (search) and resource (PDFs). It distinguishes itself from sibling tools that deal with listing or ingestion.

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 when-to-use scenarios (facts, quotes, definitions, page citations, named sections) and when-not-to-use (general knowledge, code tasks). Includes an alternative action: 'call list_documents first' if unsure.

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