City By Api Ninjas MCP Server

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, yet it reveals nothing about whether this is a read-only query, what data structure it returns, pagination behavior, or error conditions. The agent cannot determine if this is a safe operation or what side effects might occur.

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?

While the description is brief (5 words), it represents under-specification rather than efficient conciseness. The single sentence fails to earn its place by providing actionable information about the tool's functionality, wasting the opportunity to guide the agent.

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 tool with 9 parameters and no output schema or annotations, the description is woefully incomplete. It fails to explain the query logic (how filters combine), the return format, or the relationship to the API Ninjas service, leaving critical gaps in the agent's understanding.

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 input schema has 100% description coverage, documenting all 9 parameters (name, country, population ranges, coordinates, limit) adequately. The description adds no parameter-specific context, but the high schema coverage establishes a baseline score of 3 as per the evaluation guidelines.

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 'API Ninjas City API endpoint' is tautological, restating the tool's category without specifying what action it performs (e.g., search, retrieve, list). While it identifies the external service provider (API Ninjas), it lacks a specific verb or clear statement of what the tool does with city data.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as API keys, rate limits, or required parameter combinations. With no sibling tools to differentiate from, this represents a complete absence of usage guidance.

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