editMessageLiveLocation

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

No annotations are provided, so the description carries the behavioral transparency burden. It discloses the temporal edit constraint, the stopMessageLiveLocation escape hatch, and the return behavior for inline vs. non-inline messages. It omits permissions and failure modes, but the core side effects and boundaries are clearly stated.

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 compact sentences with no fluff. The core operation is front-loaded, followed by the key boundary condition and return type. Every sentence earns its place.

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 11 parameters, a nested reply_markup object, and no output schema, the description supplies essential lifecycle and return-value context that the schema cannot convey. It does not mention every restriction, such as the message having been sent by the bot, but the rich schema plus focused description is largely sufficient.

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%, so the schema already documents each parameter and its conditional requirements. The description adds no parameter-level detail, which is acceptable given the high schema coverage baseline.

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 a specific verb ('Edit') and resource ('live location messages'), which clearly distinguishes it from sibling edit tools like editMessageText and editMessageMedia. The lifecycle sentence about live_period and stopMessageLiveLocation further anchors exactly which messages this tool targets.

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 gives clear usage context by explaining when editing is allowed (until live_period expires or stopMessageLiveLocation is called). It does not explicitly exclude sibling tools like editMessageText or editMessageCaption, but the context strongly implies this is only for live location messages.

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