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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Fetch' which implies a read operation, but it does not mention response format, error behavior (e.g., missing slug), or any side effects. The minimal description leaves the agent to assume typical GET semantics without explicit confirmation.

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, front-loaded sentence with no wasted words. It efficiently conveys the core action and key parameter. However, it is so terse that it omits essential details (like the lang parameter), which slightly reduces its value, though this is more a completeness issue than conciseness.

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 two parameters (slug and lang) and no output schema, the description is incomplete. It fails to mention the language parameter, the nature of a valid slug, or any expectations about the returned entry. For an agent to call this correctly, it needs more context on parameter semantics and output.

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 description coverage is 0%, and the description adds no meaning beyond the schema. It does not explain what a 'slug' is (format, source, or uniqueness), nor does it mention the 'lang' parameter at all. The description fails to compensate for the schema's lack of documentation.

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 action (fetch), the resource (one Mavi Koy coastal atlas entry), and the lookup key (by slug). It differentiates from siblings like search_mavi_koy (which searches) and get_place (generic place), making the tool's specific scope unambiguous.

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 like get_place or search_mavi_koy. It does not mention that a slug is required to fetch a specific entry, nor does it explain scenarios where this tool is preferred over searching.

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