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

Annotations already declare a non-read-only, non-destructive, open-world operation; the description adds that the token is validated and that message routing for the project gets wired up, which is real context beyond the hints. It still omits what happens if the token is invalid and whether re-running is safe or required, so it is not fully transparent.

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, with the action front-loaded and the operational note ('run once after connecting') placed last where it belongs. No filler or restatement of the title.

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?

For a parameterless one-shot setup tool with no output schema, the description covers what it does, what it affects, and when to invoke it. The remaining gap is failure/precondition handling — what 'la connexion' must already exist and what a failed token verification looks like.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly implies the bot credentials/target project come from existing configuration rather than from arguments.

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 gives a concrete verb pair (verify the bot token, link its messages to the project) plus the downstream behaviors it enables (subscriptions, replies, /stop), which separates it from siblings like send_telegram or get_telegram_invite_link. It never names an alternative explicitly, so differentiation is implied rather than stated.

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?

'À lancer une fois après la connexion' is explicit timing guidance that tells the agent this is a one-shot post-connection step, not a repeatable action. There are no when-not conditions or named alternatives, which keeps it short of a 5.

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