MCP-Saptiva

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 mentions the efficiency advantage over individual calls, which is useful context, but doesn't address other important behavioral aspects like rate limits, error handling, response format, or any constraints on batch size. The description adds some value but leaves significant gaps.

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 perfectly concise with just two sentences that each earn their place: the first states the core functionality, and the second provides the key comparative advantage. There's zero wasted language and it's front-loaded with the essential 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?

Given the tool has no annotations and no output schema, the description should do more to compensate. While it clearly explains the purpose and when to use it, it doesn't describe what the embeddings look like, any limitations or constraints, or what happens in error cases. For a batch processing tool with no structured behavioral information, this leaves important gaps.

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 schema description coverage is 100%, with the single parameter 'texts' fully documented in the schema as 'Array of texts to convert to embeddings'. The description adds no additional parameter information beyond what's already in the schema, so it meets the baseline for high schema coverage without adding extra 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 specific action ('Generate embeddings for multiple texts at once') and the resource ('texts'), and explicitly distinguishes it from its sibling tool 'saptiva_embed' by noting it's more efficient for batch processing. This provides perfect clarity about what the tool does and how it differs from alternatives.

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 explicitly states when to use this tool ('for multiple texts at once') and provides a clear alternative ('calling saptiva_embed multiple times'), with the efficiency comparison guiding the user toward this tool for batch scenarios. This gives complete guidance on tool selection.

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