Combined MCP Server

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: it's a complex multi-step process involving downloading, processing, embedding generation, and storage. However, it doesn't mention potential side effects (e.g., overwriting existing data), performance characteristics (time/rate limits), authentication requirements, or error handling - significant gaps for a tool with no annotation coverage.

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 efficiently structured in two sentences: the first states the core purpose, the second elaborates the multi-step process. Every phrase adds value - 'from S3 markdown files,' 'configured S3 location,' and the specific technologies used (AWS Bedrock Titan, PostgreSQL) provide essential context without redundancy.

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 this is a complex data processing tool with no annotations but with an output schema, the description provides good coverage of the operation's purpose and steps. It explains the source (S3 markdown), processing (chunking), embedding generation (AWS Bedrock Titan), and storage (PostgreSQL). The output schema will handle return values, so the description appropriately focuses on the transformation process rather than output details.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters, instead focusing on what the tool does. A baseline of 4 is appropriate for zero-parameter tools where the description doesn't need to compensate for schema gaps.

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 specific action ('build or rebuild') and target resource ('knowledge base vector store'), with detailed explanation of the multi-step process. It distinguishes this tool from siblings like 'get_vectorstore_status' (monitoring) and 'query_vectorstore' (querying) by emphasizing creation/regeneration from source files.

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 context through phrases like 'from S3 markdown files' and 'configured S3 location,' suggesting this is for initial setup or refresh operations. However, it doesn't explicitly state when NOT to use this tool or name specific alternatives among siblings, though the distinction from query/monitoring tools is clear from their names.

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