telegram_status

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

Description states it returns status, implying a read-only operation. However, no annotations are provided, so the description does not disclose whether authentication is required, side effects, reliability, or response format. Basic transparency is present but insufficient for complete understanding.

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?

Single sentence, front-loaded with the purpose. Every word contributes meaning. No fluff or repetition. Ideal conciseness for a simple tool.

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 zero-parameter tool with an output schema, the description adequately states the purpose. However, it lacks usage guidance and does not mention the output schema even though it exists. Overall adequate but not comprehensive.

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?

No parameters exist in the input schema, so schema description coverage is trivially 100%. The description adds no param-specific info, which is appropriate. Per rubric, zero parameters yields baseline 4.

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 it returns login/collection status and background collection daemon status. Verb 'returns' specifies a read operation. This distinguishes it from sibling tools which perform specific actions like adding aliases, blocking names, or collecting history.

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. Does not specify typical use cases (e.g., health check) or when not to use. The description only states what it does, not the context of use.

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