telegram_status

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

Without annotations, description carries transparency burden. It discloses that no messages are sent and returns username/id, which is a read-like operation. However, it doesn't confirm no side effects or explicitly state read-only, nor describe behavior on failure.

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?

One sentence, no wasted words, front-loaded. Slightly fragmented but efficient.

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?

Description leaves significant gaps: no parameter explanation, no error behavior, no output structure despite output schema existing. For a simple tool, it's minimally adequate but not complete.

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?

0% schema description coverage and the description fails to mention or explain the sole parameter 'group_id'. Parameter semantics are completely absent.

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 tool returns bot connection status (username/id) and clarifies it does not send messages. Distinguishes it from message-sending tools, though the exact meaning of 'status' could be more specific.

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 on when to use this tool vs alternatives like telegram_commands_get or telegram_restart. Description implies usage for checking bot identity but doesn't provide context or exclusions.

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