mailkite_semantic_search

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

The description claims both 'no authentication required' and 'Requires an API key', which is internally contradictory and undermines trust. It adds 'hybrid vector + keyword search' and 'public', but the readOnly annotation already conveys safety. Lacking clear auth behavior and any disclosure about result count, pagination, or output shape, this is a low transparency score.

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 core purpose is in the first clause, sentence count is low, and the text is compact. The contradictory second sentence wastes a little value but overall the description is relatively concise and front-loaded.

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?

For a single-parameter search tool with no output schema and simple behavior, the description covers the essential request semantics but omits a concrete description of the response format, result count, or any rate-limit/pagination guidance. Since the output schema is absent, the description should have provided a bit more, but the tool's low params keep this at a mid score.

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 coverage is 100% but the schema only says 'Query parameter query.' The description adds meaningful semantics by explaining the query should be a natural-language query and that it is used to retrieve documentation sections, which goes beyond the structured info.

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?

Description names a specific verb-resource pair ('semantic search over the MailKite documentation') and explicitly states the return object ('most relevant doc sections'). It is clearly distinct from the many action-oriented sibling tools, so an agent can immediately identify this as the documentation lookup/search tool.

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?

It indicates the tool is for natural-language queries against docs, which implies when to use it, but it does not explicitly state when not to use it or name any alternative (e.g., 'use mailkite_get_template for template details'). The context is mildly helpful but not a strong routing guide.

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