Manticore Search MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully specifies the return format (JSON string with table names and types), but omits safety characteristics (read-only), rate limits, or error conditions that annotations would typically cover.

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?

Extremely concise with two distinct, information-dense segments: purpose declaration and return value specification. No redundant or filler text; every sentence earns its place.

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 tool's simplicity (zero parameters) and existence of an output schema, the description adequately covers the essential contract. However, the absence of usage guidance and behavioral annotations leaves minor gaps in contextual completeness for an agent deciding between discovery tools.

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?

Zero parameters present, which per calibration establishes a baseline of 4. The description correctly omits parameter discussion since none exist, and the schema coverage is trivially complete at 100%.

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 verb (List) and resource (tables/indexes in Manticore Search), providing specific context. However, it does not explicitly differentiate from sibling 'describe_table' (list vs. describe single table), though the distinction is implied by the verb choice.

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?

No guidance provided on when to use this versus 'describe_table' or 'run_query'. For example, it does not indicate whether this should be called before querying or how it relates to schema discovery workflows.

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