telegram_get_me

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

With no annotations available, the description carries the burden of explaining behavior. It accurately frames the operation as a read-only retrieval and token validity test, and it states what is returned. It does not explicitly say 'no side effects,' but the use of 'Get' and 'Tests' makes the non-mutating nature clear.

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 with no filler. It front-loads the action and resource, then immediately adds the token validation purpose and the returned fields, making every sentence earn its place.

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 there are no parameters camiseta an output schema exists, the description covers what an agent needs to decide whether to invoke this tool. It explains the identity retrieval, the validation behavior, and the specific data returned, so nothing essential is missing.

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 input schema has zero parameters locked in properties, so there is no parameter ambiguity to resolve. The description adds useful context about what the call returns, fulfilling the baseline expected for a parameterless tool.

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 identifies the tool as retrieving the current bot identity and configuration status, with a specific verb ('Get') and resource. It also enumerates the returned fields (bot id, username, first name, permissions), which differentiates it from the message- and chat-focused sibling 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?

The description provides a clear use case: test bot token validity and retrieve identity information. It does not explicitly name alternatives or exclusions, but since no sibling tool overlaps with this purpose, the usage context is sufficient.

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