kopern_connect_telegram

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

Annotations indicate it is a mutation (readOnlyHint=false) and idempotent (idempotentHint=true). The description adds the prerequisite of a bot token but does not discuss behavior on failure, duplication, or side effects beyond the connection action. With annotations already covering idempotency, the description adds modest value.

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 a single sentence that conveys the core purpose and a key prerequisite. It is free of filler and efficiently sized for the tool's simplicity.

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 simple two-parameter connection tool with no output schema, the description covers the essential action and prerequisite. However, it omits what the result of the operation is (e.g., confirmation or error) and does not leverage the idempotent annotation to clarify reconnection behavior. Adequate but not fully rounded.

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 already describes both parameters (agent_id and bot_token) with full coverage. The description's mention of the bot token from @BotFather repeats schema info without adding further meaning. Baseline score of 3 is appropriate given high schema coverage.

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 uses a specific verb 'Connect' and clearly identifies the resource as 'agent to Telegram via a bot'. It distinguishes from sibling connect tools like connect_calendar or connect_email by naming the Telegram platform and mentioning the bot token requirement.

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 implies the tool is for setting up Telegram integration but does not explicitly state when to use it over alternatives. The prerequisite 'Requires a bot token from @BotFather' gives some context, but no guidance on when to choose this tool vs other connection tools or when not to use it.

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