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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read behavior is known. The description adds that the return value is an HTML snippet plus public site id and where it should be pasted. No contradictions, but it does not disclose any caveats beyond that.

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 short sentences: the first states the output precisely and the second gives placement guidance. No filler or redundant details.

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 zero-parameter, read-only tool, the description covers the main purpose slash output and usage context. It does not detail the exact HTML shape or whether the snippet requires authentication, but with no parameters and readOnly annotations, enough context is present for an agent to use it.

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 is empty with 100% coverage and zero parameters, so no parameter documentation is needed. The description correctly avoids inventing parameters and instead focuses on the returned artifact.

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 identifies the resource (embed code for this locator) and the verb is implied by the title ('Get'). It also adds concrete detail: the output is an HTML snippet plus a public site id, which distinguishes it from sibling tools like get_location that return different 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?

It conveys the usage context: the embed code is meant to be pasted into a website where the map should appear. It does not explicitly enumerate alternatives or when-not-to-use, but for a zero-parameter retrieval tool this is adequate.

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