telegram-get-contacts

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by revealing that phone numbers are included in the results, which is a specific behavioral trait not covered by annotations. No contradictions with annotations.

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 single sentence conveys the entire purpose without any fluff or repetition. Every word is necessary and contributes to clarity.

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 read-only tool with one optional parameter and safety annotations, the description is mostly sufficient. It does not detail the return format (e.g., fields of each contact), but the output is largely implied. Slightly more context about scope (e.g., 'your own contacts') would improve completeness.

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 provides 100% coverage with a clear description for the 'limit' parameter ('Number of contacts to return'). The tool description does not add any additional meaning or constraints beyond the schema, so it meets the baseline for 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 clearly states 'Get your Telegram contacts list with phone numbers', specifying the verb 'Get', the resource 'contacts list', and an important detail (phone numbers). It distinguishes this tool from sibling tools like 'telegram-add-contact' or 'telegram-get-contact-requests' which serve different purposes.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations (e.g., only returns own contacts), or when not to use it. Among many sibling tools, this lack of context could confuse an AI agent.

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