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

Annotations already establish that this is a non-readonly, open-world, non-idempotent, non-destructive write. The description goes beyond that by disclosing the fixed recipient, the 4096-character auto-splitting behavior, and a content restriction on emoji. It omits failure modes, rate limits, and whether delivery is confirmed, which keeps it short of a 5.

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?

Three short sentences, no filler, and the most important constraint (fixed recipient) is front-loaded in a parenthetical before any formatting rules. Every sentence carries an actionable constraint.

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 three-parameter, single-purpose tool with full schema coverage and no output schema, the description covers recipient, length handling, and content restrictions adequately. What is missing — delivery confirmation, failure behavior, rate limits — is minor given the tool's simplicity.

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?

Schema coverage is 100% and each parameter carries its own description, so the baseline is 3. The description's 4096-character split rule is genuinely useful context for the text parameter because the schema only advertises maxLength 40000, but the emoji ban and split threshold are the only added meaning; format and silent are left entirely to the schema.

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 specific verb and resource ("Sends a message to the owner's Telegram") and immediately scopes the recipient as a fixed chat, which separates it in practice from notify_file. It does not name the sibling explicitly, so the differentiation is inferred from the resource 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?

"You cannot choose the recipient" rules out an approach an agent might otherwise attempt, and "Do not use emoji or icons" is a usable constraint. However, there is no statement of when to prefer notify_file over notify, and no guidance on when a notification is appropriate at all — usage is implied rather than specified.

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

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

Annotations already say the tool is a non-read-only, open-world, non-idempotent write, but nothing in them reveals that it is unusable in this deployment. The description supplies exactly that operational fact, which is the single most important behavioral trait here, though it does not say what the refusal looks like (error vs. empty result).

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 short sentence that puts the blocking fact first with no filler. Nothing in it could be removed without losing the warning.

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 deliberately disabled tool with full schema coverage and no output schema, telling the agent it will always be refused is nearly all that is needed. It would be complete if it pointed to the working sibling 'notify' as the fallback path.

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?

Schema coverage is 100% and all three parameters are documented in the schema, including the path restriction and the 1024-character caption split. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 never states what the tool does in active terms; the operation ('File sending') is only mentioned inside a statement that it is disabled. An agent learns the resource but not the verb or outcome, and must fall back on the title 'Send a file over Telegram' for the actual purpose.

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?

It gives an unusually decisive usage rule: every call is refused, so the tool should not be invoked at all. That is explicit when-not-to-use guidance, though it stops short of naming the sibling 'notify' as the alternative for text messages.

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