telegram-send-location

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

Annotations already flag write operation. Description adds: default static, livePeriod enables live sharing. Does not detail return behavior or permissions, but covers key behavioral nuance.

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 sentences, no wasted words. Main action front-loaded, live variation clearly explained.

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 170+ siblings and a fully documented schema, the description is sufficient. No output schema but parameters are self-explanatory. Missing return value info but acceptable.

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?

Input schema covers all 9 parameters with descriptions; description adds no new parameter meaning beyond reiterating livePeriod purpose. Baseline 3 is appropriate.

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?

Description clearly states the action ('send a geographic location'), target ('Telegram chat'), and distinguishes between static and live location via 'livePeriod'. No ambiguity among sibling send tools.

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?

Implicitly when to use (sharing a location). Does not explicitly mention when not to use or compare with 'telegram-send-venue', but the parameter description of 'livePeriod' provides context for choosing static vs live.

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