edit_message_live_location

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It conveys the core action and the live-period constraint but does not discuss side effects, authentication needs, rate limits, or what happens to the previous location. Some transparency is present, but gaps remain.

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 two sentences, concise and front-loaded with the core purpose. Every sentence adds value without unnecessary 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?

The description covers the essential constraint (live location) and the chat_id default, but it lacks information about conditional parameter requirements (message_id vs inline_message_id) and expected outcomes (e.g., success response). For a 9-parameter mutation tool without output schema, more context would improve completeness.

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 coverage is 100%, so each parameter is documented. The description adds value by explaining the default log group behavior for chat_id, which complements the schema. This extra context improves semantic understanding beyond the schema descriptions.

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 tool edits a live location message and specifies the prerequisite that the message must be live. It also adds context about the chat_id defaulting to the log group, which distinguishes it from sibling tools like send_location and stop_message_live_location.

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 a clear condition (must be live location) and explains the default behavior for chat_id. However, it does not explicitly mention when to use this tool over alternatives like edit_message or stop_message_live_location, nor does it advise against use for non-live messages.

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