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

With no annotations and no description, the tool's behavior is entirely opaque. It is unclear whether this is a read-only search operation, whether it has side effects, or what the output format is. No safety information is disclosed.

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 a single short sentence, which is concise, but it sacrifices all informative value. It does not explain the parameters, the search scope, or any filtering logic, making the brevity a liability rather than a strength.

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?

The tool is severely under-described. With no parameter explanations, no usage context, and no output schema, an agent has no way to correctly invoke this tool or interpret its results. It is far from complete.

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?

All five parameters (q, lang, limit, region, category) are listed in the schema but none are described. The schema provides types and constraints but gives no semantic meaning, leaving the agent to guess how to construct a valid query.

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 states it searches 'Mavi Koy public coastal atlas entries' but does not clarify what these entries are or how they differ from the sibling search tools like search_places and search_dishes. The purpose is too vague to be actionable.

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 is provided on when to use this tool versus the many sibling search tools (e.g., search_places, search_dishes). The description lacks any context about the intended use case or selection criteria.

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