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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds behavioral details about the content returned (status, alerts, hazards, load, traditional knowledge) without contradicting annotations. It doesn't mention potential limitations or performance considerations, but for a read-only context tool this is acceptable.

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 concise—two sentences—with the core purpose and usage guideline front-loaded. Every word adds value, and it avoids redundancy with schema or annotations.

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?

No output schema exists, but the description enumerates the key information returned, which is helpful. It doesn't specify exact formatting or error scenarios, but for a read-only single-parameter tool, the description covers the essentials. A brief note on prerequisites or typical use cases could enhance completeness, but it's not critical.

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 schema provides 100% coverage for the single parameter 'place' with a description ('Название места или объекта'). The tool description does not add any further semantic detail about the parameter, so it relies entirely on the schema. Baseline 3 is appropriate.

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 it retrieves comprehensive context about a place, listing specific data types (status, real-time alerts, hazards, load, traditional knowledge). It distinguishes itself from siblings like get_place_info by focusing on Guardian context, and the title 'Безопасность места' reinforces the safety-focused purpose.

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?

Explicitly instructs to use this tool whenever a specific place, volcano, lake, route, or source in Kamchatka is mentioned. The 'always' directive gives strong guidance, though it doesn't explicitly contrast with alternatives like get_place_info or safety_status, leaving some ambiguity for overlapping tools.

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