stop_message_live_location

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the non-destructive mutation is known. However, the description adds no further behavioral context, such as that the message remains intact, that updates cease permanently, or that ownership/permissions are required.

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 a single, direct sentence with no superfluous words. It is appropriately front-loaded and easy to parse, which is ideal for a simple tool.

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 4 parameters, 0 required, no output schema, and no usage guidance, the description alone is insufficient for an agent to confidently invoke the tool. The parameter combination logic and expected behavior are not disclosed, making successful use reliant on external knowledge.

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 75%, so the schema already documents most parameters, but the description itself adds no parameter meaning. It does not clarify the alternative between chat_id+message_id and inline_message_id, nor why no parameters are required, leaving ambiguity for invocation.

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 uses a specific verb 'Stop' and a clear resource 'a live location message,' which precisely states the tool's function. It distinguishes from the sibling edit_message_live_location by indicating the action is to cease updates rather than modify them.

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 no guidance on when to use this tool over alternatives, such as edit_message_live_location, nor does it mention prerequisites like needing an existing live location message or the chat_id/inline_message_id distinction. No exclusions or alternative tool references are provided.

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