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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it says nothing about read-only nature, return format, permission requirements, or error behavior. 'Map detail' discloses no behavioral traits whatsoever.

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?

Two words contain no filler, but this is under-specification rather than conciseness. The brevity omits information the agent needs rather than trimming redundant content.

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?

With no annotations, no output schema, and a two-word description, the definition is completely inadequate for an agent to call the tool correctly. Nothing about the return shape or the relationship to the many sibling map tools is conveyed.

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 100%, with both the slug format ('e.g. prokhorovka') and the region enum fully documented in the schema. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 'Map detail' merely restates the tool name (maps_by_slug) without a specific verb or any scoping information. It gives no indication of what distinguishes it from siblings like maps_by_slug_history, maps_by_slug_ratings, or og_maps_by_slug.

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?

There is no guidance on when to use this tool versus alternatives. An agent has no way to know whether maps_by_slug or og_maps_by_slug or maps_search is the correct entry point.

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