send_location

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

Annotations already indicate a write operation (readOnlyHint=false). The description adds the meaningful detail that setting live_period (60-86400) sends a live location. However, it does not disclose other behavioral aspects such as whether silent affects delivery or whether the chat must be a group or private conversation.

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 brief and front-loaded with the purpose. The Args section is minimal and directly useful, and every sentence earns its place without redundancy or filler.

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?

Given the tool has 5 parameters (3 required) and an output schema, the description is too sparse. It omits essential context about required parameters, the meaning of silent, and how to specify the chat target. The live_period detail is helpful, but overall the description does not provide sufficient guidance for an agent to confidently invoke the tool.

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 has 0% description coverage, and the description only explains live_period. It does not clarify the format or meaning of chat, latitude, longitude, or silent. While latitude and longitude are self-explanatory, the chat field's anyOf type and silent's effect are left undocumented, making parameter understanding incomplete.

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 action (send) and the resource (geolocation), which is specific and distinguishes it from sibling send tools like send_message or send_contact. The purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as send_message or send_contact. The only usage hint is the live_period parameter behavior, but there is no mention of prerequisites, chat requirements, or scenarios where this tool is preferred.

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